Messages in this thread | | | Date | Thu, 20 Feb 2003 07:23:23 +0100 | From | Jan-Benedict Glaw <> | Subject | Re: 2.5.61 (Yes, there are still Alpha users out there. :-) ) |
| |
On Wed, 2003-02-19 15:39:44 -0500, Bill Davidsen <davidsen@tmr.com> wrote in message <Pine.LNX.3.96.1030219153452.11297B-100000@gatekeeper.tmr.com>: > On Wed, 19 Feb 2003, Jan-Benedict Glaw wrote: > > On Wed, 2003-02-19 13:00:39 -0500, Bill Davidsen <davidsen@tmr.com> > > > Be aware that for Redhat and SuSE distributions (and mandrake??) "make > > > install" will fail because mkinitrd doesn't know about the new modules > > > format. > > > > > > So you can give up using modules for anything you want to use to boot, > > > > Which is what I prefer - I personally don't like initrd and I don't use > > it. > > If you have simple needs that's fine. I build for multiple groups of > machines, and with a working mkinitrd I can just build a file for the boot > controller on each type of machine, and only build a single kernel which > will run anywhere with the proper initrd file.
I do it the other way around - I've collected a number of .config files (one for each machine) which includes everything the machine needs to *boot*. Any additional features (LVM/DM, filesystems, iptables, ...) ships as modules. Things which require a distinct order are placed into /etc/modules (Debian's list of modules which need to be loaded in given order), all the rest is done via alias/install lines in modules.conf/modprobe.conf.
This is, you do keep a machine's local config in its initrd, I do keep it on the machine itself.
MfG, JBG
-- Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur fuer einen Freien Staat voll Freier Bürger" | im Internet! Shell Script APT-Proxy: http://lug-owl.de/~jbglaw/software/ap2/ [unhandled content-type:application/pgp-signature] | |