--=_courier-26302-1045687458-0001-2
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Content-ID: <Pine.LNX.3.96.1030219153452.11297D@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.
using initrd files also allows easy control of the order in which SCSI
controllers are loaded, which prevents drives from changing names.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.--=_courier-26302-1045687458-0001-2--