On Wed, May 26, 2004 at 07:47:47AM +0200, Sven Luther wrote: > On Tue, May 25, 2004 at 10:22:25PM +0200, Jens Schmalzing wrote: > > No. The initrd should only contain the modules needed for bringing up > > the root filesystem, and maybe using the console. It is mkinitrd's > > duty to figure out what's needed. If the resulting initrd doesn't > > work, it's a bug in mkinitrd and needs to be fixed. > > Yeah, sure, but i think there is a misunderstanding. the duty of > discover is exactly to find the modules needed by your system and load > them. Exactly the same thing mkinitrd does (or more exactly the the > /bin/init script of the initrd), just in a bigger scale. It is my > understanding that if discover is used together with a smaller database > of modules, well, including only those modules that get needed, then it > would do the same job as the current init script, without duplicating > the effort needed to identify and locate modules twice. Remember that > discover is used in the debian-installer initrd, so why should it not > also work for us ? Why not use discover in mkinitrd instead? With this solution you can have both, a small initrd without bloat and automatic detection of moudules needed to boot the system.
Gaudenz
signature.asc
Description: Digital signature
