Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: Initramfs | Date | 28 Aug 2003 13:07:03 -0700 |
| |
Followup to: <3F44D504.7060909@pobox.com> By author: Jeff Garzik <jgarzik@pobox.com> In newsgroup: linux.dev.kernel > > Bryan O'Sullivan wrote: > > No. initramfs is stuck in limbo at the moment, and early userspace is > > unlikely to see any real work until 2.7. Feel free to ask questions, > > but don't expect them to result in anything actually happening. > > > > If you want to do real work in this area, the klibc mailing list is the > > place to go: http://www.zytor.com/mailman/listinfo/klibc > > Correct, though there is one thing I am thinking about adding to 2.6: > > Support replacing "initrd=" with "initramfs=", so that bootloaders can > pass a cpio image into the standard initrd memory space. >
Note that the initrd= option is actually a boot loader option, not a kernel option, so the name of the option shouldn't change.
But yes, an initramfs image loaded into initrd space should be unpacked *on top of* what's already compiled into the kernel.
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! If you send me mail in HTML format I will assume it's spam. "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64 - 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/
| |