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?

> 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 <[EMAIL PROTECTED]>
>
> 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.

> -               printk(KERN_INFO "Unpacking initramfs...");
> +              printk(KERN_INFO "Unpacking initrd...");
>                 err = unpack_to_rootfs((char *)initrd_start,
>                         initrd_end - initrd_start, 0);
>                 if (err)
>
> -


Thanks!

--
Al

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to