Messages in this thread | | | Subject | Re: [PATCH]: typo in init/initramfs.c | From | Jean-Paul Saman <> | Date | Mon, 11 Dec 2006 10:34:10 +0100 |
| |
linux-kernel-owner@vger.kernel.org wrote on 08-12-2006 14:58:24:
> Jean-Paul Saman wrote: > > linux-kernel-owner@vger.kernel.org wrote on 06-12-2006 19:17:27: > > > Jean-Paul Saman wrote: > > > > In populate_rootfs() the printk on line 554. It says "Unpacking > > > > initramfs..", which is confusing because if that line is reached the > > > > code has already decided that the image is an initrd image. > > > > > > Are you sure? > > > > Yes. > > Are you really sure? >
Not anymore ;-)
> Maybe you're getting confused with the dual intitrd naming-convention. > InitRD used to mean InitRamDisk only, now it means InitRamFS and InitRamDisk > #ifdef CONFIG_BLK_DEV_RAM, else it means InitRamFS only.
Well, I am confused. Reading drivers/block/Kconfig again and again I came to the conclusion that I've been misinterpreted what it said. The way the code is written is counter-intuitive, using INITRD for initramfs and initrd made my head go spinning.
> But still, it's rather refreshing to see you so convinced.
Thanks for your kind words.
Kind greetings,
Jean-Paul Saman
NXP Semiconductors CTO/RTG DesignIP
- 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/
| |