lkml.org 
[lkml]   [2006]   [Dec]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH]: typo in init/initramfs.c
From
Date
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/

\
 
 \ /
  Last update: 2006-12-11 10:37    [W:0.040 / U:0.176 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site