Re: Building Your own Boot Disks
-BEGIN PGP SIGNED MESSAGE- On Thu, 21 Aug 1997, Timm Gleason wrote: > I cannot get the modules to install. > >"modprobe: error reading ELF header: no such file or directory" The new modprobe will complain if informative files like BLOCK_MODULES and the like are contained in /lib/modules/2.x.x/ Throw those out and your modules.tgz will be accepted. (To make those automatically upgrade your 'kernel-package') Nils - -- \ /| Nils Rennebarth --* WINDOWS 42 *-- | Schillerstr. 61 / \| 37083 Göttingen | ++49-551-71626 Micro$oft's final answer | http://www.nus.de/~nils -BEGIN PGP SIGNATURE- Version: 2.6.3i Charset: noconv iQB1AwUBNAKmXFptA0IhBm0NAQGz/QL8DH/IeslLW5+0MEKDdoB/rKZB4V6KkIJQ dMMxNJmARzSC8mnC5Il8NiB1FgZr2yILg5QG2m2rDY/o2iteuzlbLRGKSzSc/ui8 R6nHDZrPxUXi7fH5iNjLECkAXfyiI9Vw =oxZX -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Building Your own Boot Disks
On Thu, 21 Aug 1997, Paul Wade wrote: > On Fri, 22 Aug 1997, Craig Sanders wrote: > > > imo, everyone should compile their own kernel - the boot/rescue floppy > > is good to install a system with, but a linux box really should have a > > kernel compiled especially for itwith only the drivers that it needs > > compiled in (or as modules), no more and no less. > > Often true, but it is better to use kernel-package which builds a Debian > kernel-image package for this. yes. "...compile their own kernel" includes the possibility of using make-kpkg. in fact, earlier in my message that is exactly what i said i had done. my point was that if you want to get the most out of your linux box then compiling your own kernel is essential. it doesn't really matter whether that is done with the old "make zlilo ; make modules ; make modules_install" (or whatever) sequence of commands, or whether it's done with kernel-package. i happen to think that kernel-package is much more convenient. some people think otherwise. big deal, it doesn't matter which way it's done. > One great reason is that you can build these packages on a machine > that has all the tools and compiles fast. The resulting .deb file is > easily installed with dpkg and will take care or making the hard disk > boot the new kernel (while preserving the previous one) and creating a > boot floppy. yes, kernel-package is a great tool. craig -- craig sanders networking consultant Available for casual or contract temporary autonomous zone system administration tasks. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Building Your own Boot Disks
On Thu, 21 Aug 97 16:51 PDT, Bruce Perens <[EMAIL PROTECTED]> wrote: >From: [EMAIL PROTECTED] (Timm Gleason) >> Now not wanting to go backward, especially due to the >> major modifications done to the kernel we are using > >Is that the BESS Internet filter? I hope your product still lets you read >the list, after the language we've been using on debian-user today :-) >15-20 a month and Debian in every one? Cool! > Yes, we use Linux servers for all of our on-site and redirect proxy servers. We have been using Debian from the beginning because of the amount of stability and support available. >If you're developing big changes to the kernel, please try to contribute >them back into the main kernel source thread. > Most of the hacks into the kernel involve max file descriptors and inodes to allow for greater simultaneous connections. Almost all of the modifications we have made the real work has been done by someone else out there. We can get near 1500 simultaneous connections with the kernel we currently use. >> like to know if there is any definitive source of information on >> building installation disks. The new system that loads base off of a >> CD is great, but with the modified drivers and kernel, I need to know >> more about these disks. > >Sure. You will need two packages: kernel-package and boot-floppies. >Kernel-package provides the scripts to build a Debian package from >your custom kernel and calling them from the command line is trivial. >Boot-floppies provides the scripts to build the boot floppies, and you >can easily modify that or just change the packages it installs. You will >also need a complete copy of the Debian "stable" archive plus your >modifications, and you will need to read the man page for dpkg-scanpackages >(in the dpkg-dev package) so that you can add your own packages to the >"Packages" file for your own archive, so that dpkg and dselect will work with >it. > >Once you've done that, you can install the debian-cd package and generate your >own bootable CDs with your custom kernel if you wish. > Burn our own bootable CD's, wow that would be even better than what we do now! Timm Gleason ** "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rich Cook ** Timm Gleason -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- http://n2h2.com/ N2H2, Creators of Bess -- 1301 Fifth Avenue, Suite 1501--Seattle, WA 98101 ** -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Building Your own Boot Disks
On Fri, 22 Aug 1997, Craig Sanders wrote: > imo, everyone should compile their own kernel - the boot/rescue floppy > is good to install a system with, but a linux box really should have a > kernel compiled especially for itwith only the drivers that it needs > compiled in (or as modules), no more and no less. Often true, but it is better to use kernel-package which builds a Debian kernel-image package for this. One great reason is that you can build these packages on a machine that has all the tools and compiles fast. The resulting .deb file is easily installed with dpkg and will take care or making the hard disk boot the new kernel (while preserving the previous one) and creating a boot floppy. Manoj even helped me get a shell script going that will rebuild several custom kernels at a time. His kernel-package is a big help to me as I have several old machines that would take a few hours to build a kernel on. +--+ + Paul Wade Greenbush Technologies Corporation + + mailto:[EMAIL PROTECTED] http://www.greenbush.com/ + +--+ + http://www.greenbush.com/cds.html Now shipping version 1.3.? + +--+ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Building Your own Boot Disks
From: [EMAIL PROTECTED] (Timm Gleason) > Now not wanting to go backward, especially due to the > major modifications done to the kernel we are using Is that the BESS Internet filter? I hope your product still lets you read the list, after the language we've been using on debian-user today :-) 15-20 a month and Debian in every one? Cool! If you're developing big changes to the kernel, please try to contribute them back into the main kernel source thread. > like to know if there is any definitive source of information on > building installation disks. The new system that loads base off of a > CD is great, but with the modified drivers and kernel, I need to know > more about these disks. Sure. You will need two packages: kernel-package and boot-floppies. Kernel-package provides the scripts to build a Debian package from your custom kernel and calling them from the command line is trivial. Boot-floppies provides the scripts to build the boot floppies, and you can easily modify that or just change the packages it installs. You will also need a complete copy of the Debian "stable" archive plus your modifications, and you will need to read the man page for dpkg-scanpackages (in the dpkg-dev package) so that you can add your own packages to the "Packages" file for your own archive, so that dpkg and dselect will work with it. Once you've done that, you can install the debian-cd package and generate your own bootable CDs with your custom kernel if you wish. Thanks Bruce -- Can you get your operating system fixed when you need it? Linux - the supportable operating system. http://www.debian.org/support.html Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Building Your own Boot Disks
On Thu, 21 Aug 1997, Timm Gleason wrote: > We build many, many Linux boxes (on order of 15 to 20 a month). We > just received some new disk sets for Debian 1.3.1. We have been using > 1.2 and kernel 2.0.30. The new disk set comes with the disk images > having 2.0.29. Now not wanting to go backward, especially due to the > major modifications done to the kernel we are using, I cannot build a > boot disk and drivers disk that will do a good install. up until a month or two ago, i was building about 5 debian boxes per month. I just used the boot disks to do the basic install, and then used dpkg to install my custom compiled kernel (made using kernel-package's make-kpkg command). the procedure went something like this: 1. boot install floppy. install base system, reboot, run dselect, etc. 2. ftp kernel-image-XXX_XXX.deb from another machine on my network. 3. if kernel image is same version as on the install boot/rescue disk then "rm -rf /lib/modules/X.X.X" 4. dpkg -i kernel-image-XXX_XXX.deb if my custom kernel is a different version to the one on the boot floppy (usually is), then i do the following as well: 5. make a /vmlinuz.old symlink pointing to the old kernel. 6. edit lilo.conf. 7. run "lilo -t && lilo". do this and you shouldn't need to mess about with making your own boot/rescue and drivers disks. imo, everyone should compile their own kernel - the boot/rescue floppy is good to install a system with, but a linux box really should have a kernel compiled especially for itwith only the drivers that it needs compiled in (or as modules), no more and no less. > The kernel, drivers and base all install fine, however, I cannot > specify which modules I wish to use. The installation of them fails. I > receive an error message as follows: > > "modprobe: error reading ELF header: no such file or directory" your modules.tgz may have the old (and now incompatible) *_MODULES text files in the /lib/modules/X.X.X directory. try: find /lib/modules -name "*_MODULES" if they are there, then delete them by typing: find /lib/modules -name "*_MODULES" | xargs rm if this solves the problem, then create a new modules.tgz based on this. craig -- craig sanders networking consultant Available for casual or contract temporary autonomous zone system administration tasks. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Building Your own Boot Disks
We build many, many Linux boxes (on order of 15 to 20 a month). We just received some new disk sets for Debian 1.3.1. We have been using 1.2 and kernel 2.0.30. The new disk set comes with the disk images having 2.0.29. Now not wanting to go backward, especially due to the major modifications done to the kernel we are using, I cannot build a boot disk and drivers disk that will do a good install. First, I have changed the kernel out on the 1.3.1 boot/rescue disk and ran rdev.sh on it. I replaced the sys_map.gz and edited the install.sh so that VERSION=2.0.30. I replace the modules.tgz on the drivers disk with a modules.tgz that contains an updated tulip driver and all other modules have been compiled under 2.0.30. In the past this is all that i have had to do to get the disks working, now with this new version of the Debian installer, I cannot get the modules to install. The kernel, drivers and base all install fine, however, I cannot specify which modules I wish to use. The installation of them fails. I receive an error message as follows: "modprobe: error reading ELF header: no such file or directory" While I have managed to klop something together that works, I would like to know if there is any definitive source of information on building installation disks. The new system that loads base off of a CD is great, but with the modified drivers and kernel, I need to know more about these disks. Timm Gleason Hardware Engineer N2H2, Inc. ** "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rich Cook ** Timm Gleason -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- http://n2h2.com/ N2H2, Creators of Bess -- 1301 Fifth Avenue, Suite 1501--Seattle, WA 98101 ** -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
