On 04.07 Alexander Skwar wrote:
> So sprach Andrej Borsenkow am Fri, Apr 06, 2001 at 05:09:27PM +0400:
> > >
> > > This could be solved giving a pre-built initrd with kernels.
> > >
> >
> > I second that.
>
> Uhm, while this sounds nice - what do you want to put all into this generic
> initrd? There are quite some SCSI drivers out there; including them all
> will make the initrd huge, I suppose. And also include reiserfs even if
> people don't use it?
>
At least all that can be needed to boot, with some limits.
You can say: hey, do not make your /boot reiser, just ext2. But you
can't say "don't boot from your aha152x", because I can't boot from
anything else.
If <md> (raid) is worthy to be in the default kernels, I think there are
many other drivers that should also be built-in (how many people BOOTS
from raid ??).
Put in the place: you need a driver to boot, it is taken from initrd,
and you can't build a suitable initrd 'cause your running kernel loop
support is broken. After the kernel upgrade (in which mkinitrd breaks or
gets hung), your dead. No boot.
By now I have a crap ide disk in that system just to be able to boot
because ide is built-in in mdk kernels. But that is not a serious solution.
Say that to all the people with servers that boot from a 2940 and have no
ide disks...
--
J.A. Magallon # Let the source
mailto:[EMAIL PROTECTED] # be with you, Luke...
Linux werewolf 2.4.3-ac3 #1 SMP Thu Apr 5 00:28:45 CEST 2001 i686
