From: Al Boldi <a1426z@gawab.com>
To: Jean-Paul Saman <jean-paul.saman@nxp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: typo in init/initramfs.c
Date: Fri, 8 Dec 2006 16:58:24 +0300 [thread overview]
Message-ID: <200612081658.24194.a1426z@gawab.com> (raw)
In-Reply-To: <OFFC8397EF.1D0C38CD-ONC125723E.002EA3BB-C125723E.002EE367@philips.com>
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?
> > > The printk is thus
> > > wrong in stating that it is unpacking an "initramfs". It should says
> > > "initrd" instead. The attached patch corrects this typo.
> > >
> > > Signed-off-by: Jean-Paul Saman <jean-paul.saman@nxp.com>
> > >
> > > diff --git a/init/initramfs.c b/init/initramfs.c
> > > index d28c109..f6020db 100644
> > > --- a/init/initramfs.c
> > > +++ b/init/initramfs.c
> > > @@ -551,7 +551,7 @@ #ifdef CONFIG_BLK_DEV_RAM
> >
> > This is where initramfs is discerned from initrd, as both are available.
> >
> > > free_initrd();
> > > }
> > > #else
> >
> > Otherwise it's initramfs only.
>
> No otherwise it falls under CONFIG_BLK_DEV_INITRD and it that suggests it
> must be a initrd, not a initramfs as the original printk() suggests.
This is what 2.6.19 says:
=========================
#ifdef CONFIG_BLK_DEV_INITRD
if (initrd_start) {
#ifdef CONFIG_BLK_DEV_RAM
int fd;
printk(KERN_INFO "checking if image is initramfs...");
err = unpack_to_rootfs((char *)initrd_start,
initrd_end - initrd_start, 1);
if (!err) {
printk(" it is\n");
unpack_to_rootfs((char *)initrd_start,
initrd_end - initrd_start, 0);
free_initrd();
return;
}
printk("it isn't (%s); looks like an initrd\n", err);
fd = sys_open("/initrd.image", O_WRONLY|O_CREAT, 0700);
if (fd >= 0) {
sys_write(fd, (char *)initrd_start,
initrd_end - initrd_start);
sys_close(fd);
free_initrd();
}
#else // <=== of #ifdef CONFIG_BLK_DEV_RAM
printk(KERN_INFO "Unpacking initramfs...");
err = unpack_to_rootfs((char *)initrd_start,
initrd_end - initrd_start, 0);
if (err)
panic(err);
printk(" done\n");
free_initrd();
#endif // <=== of #ifdef CONFIG_BLK_DEV_RAM
}
#endif // <=== of #ifdef CONFIG_BLK_DEV_INITRD
=========================
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.
But still, it's rather refreshing to see you so convinced.
Thanks!
--
Al
next prev parent reply other threads:[~2006-12-08 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 18:17 Al Boldi
2006-12-08 8:32 ` Jean-Paul Saman
2006-12-08 13:58 ` Al Boldi [this message]
2006-12-11 9:34 ` Jean-Paul Saman
-- strict thread matches above, loose matches on Subject: below --
2006-12-06 12:46 Jean-Paul Saman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612081658.24194.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=jean-paul.saman@nxp.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®