linux-kernel - Re: [PATCH]: typo in init/initramfs.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <OF5010A572.F37D95B9-ONC1257241.0033BBE4-C1257241.0034922E@philips.com>
Date:	Mon, 11 Dec 2006 10:34:10 +0100
From:	Jean-Paul Saman <jean-paul.saman@....com>
To:	Al Boldi <a1426z@...ab.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH]: typo in init/initramfs.c

linux-kernel-owner@...r.kernel.org wrote on 08-12-2006 14:58:24:

> Jean-Paul Saman wrote:
> > linux-kernel-owner@...r.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/