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
BLK_DEV_INITRD
[ 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?
Thanks,
Grzegorz Kulewski
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |