Messages in this thread | | | Date | Tue, 11 Apr 2006 12:57:10 +0400 | From | Michael Tokarev <> | Subject | Re: Separate Initramfs dependency on initrd (and therefore ramdisks) |
| |
Kris Shannon wrote: > A number of distributions (most importantly for me - Debian) use the > initrd as initramfs facility. I assumed that the passing of the data > block would be independent of ram disks seeing as not using a ram > disk was one of the major reasons for initramfs, but it seems that > you need CONFIG_BLK_DEV_INITRD=y which depends on > CONFIG_BLK_DEV_RAM=y > > Would a patch separating out the init image handling from the initrd > handling be welcome and if so should the resulting init image code > be dependant on a CONFIG variable or always on (like initramfs is now) > > The only reference to this I found in the archives was: > > http://www.uwsg.indiana.edu/hypermail/linux/kernel/0508.1/0097.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0603.1/0969.html
/mjt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |