[klibc] Re: [PATCH - RFC] Move initramfs configuration to "General setup"

Milton Miller miltonm at bga.com
Wed Aug 10 00:52:54 PDT 2005

On Mon Aug 8 07:57:37 PDT 2005, Grzegorz Kulewski wrote:

> On Mon, 8 Aug 2005, Olaf Hering wrote:
> > On Mon, Aug 08, Grzegorz Kulewski wrote:
> >
> >>> From my recent experiments it looks like in order to be able to use
> >> initramfs not compiled into the kernel image but loaded from 
> separate file
> >> by GRUB or LILO one must also build initrd into the kernel.
> >
> > The file passed from the bootloader to the kernel, which is later
> > eventually recognized as an initrd, can be everything. But the kernel
> > code to deal with the memory range containing the file is behind
> > CONFIG_BLK_DEV_INITRD. The new config options should depend on
> [ Depend or select? ]
> So this code should be separated from initrd and put in some other 
> place
> and depend on initrd || initramfs.
> >From what I saw reading the code initrd is much more than this code 
> so why
> keep it together?

The only dependancy on BLOCK_DEV_INITRD by initramfs is that you will
end up with a /initrd.data file locked in ramfs if you miss the
format.   do_mounts_initrd is needed only for the initrd* globals
at the top, those could be moved.

In short, its easy to remove the depenancy today, there is no magic
sharing of the major number as in the past.


More information about the klibc mailing list