[Buildroot] where is the initrd image?

[Buildroot] where is the initrd image?

[Lee JJ]

Dear All Guru :

     I can generate the target achi rootfs , and kernel
but I can't find the initrd file

Thus I met the booting problem , VFS cannot open root device "hdxx"

Do I nust have the initrd file , or not ?
If do , how and where to build it ?

Thanks !!

ps: I am using buildroot snapshot , June 23 '07
and the target archi is i386
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20070627/9cb32a5d/attachment.htm 

[Buildroot] where is the initrd image?

[Julien Letessier]

As far as I known there is no support for initrd in buildroot.
And you don't need one for an embedded system!

In desktop distributions, the initrd is used e.g. to load device/filesystem
drivers before mounting the root filesystem (which may reside on a
nonstandard device/filesystem). [1]

In an embedded system, you should include all appropriate drivers in the
kernel itself, so an initrd is useless.
Just compile a proper kernel, and configure grub on your target with e.g.

kernel /boot/bzImage root=/dev/hda1

[1] http://en.wikipedia.org/wiki/Initrd

2007/6/27, Lee JJ <jengjr@gmail.com>:
>
> Dear All Guru :
>
>      I can generate the target achi rootfs , and kernel
> but I can't find the initrd file
>
> Thus I met the booting problem , VFS cannot open root device "hdxx"
>
> Do I nust have the initrd file , or not ?
> If do , how and where to build it ?
>
> Thanks !!
>
> ps: I am using buildroot snapshot , June 23 '07
> and the target archi is i386
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>



-- 
Julien Letessier
<julien.letessier@technosens.fr>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20070627/b68163c2/attachment-0001.htm 

[Buildroot] where is the initrd image?

[Bernhard Fischer]

On Wed, Jun 27, 2007 at 11:35:02AM +0200, Julien Letessier wrote:
>As far as I known there is no support for initrd in buildroot.
>And you don't need one for an embedded system!
>
>In desktop distributions, the initrd is used e.g. to load device/filesystem
>drivers before mounting the root filesystem (which may reside on a
>nonstandard device/filesystem). [1]
>
>In an embedded system, you should include all appropriate drivers in the
>kernel itself, so an initrd is useless.
>Just compile a proper kernel, and configure grub on your target with e.g.
>
>kernel /boot/bzImage root=/dev/hda1
>
>[1] http://en.wikipedia.org/wiki/Initrd

http://busybox.net/bugs/view.php?id=881

This is high on my TODO list for quite some time now, fwiw.
As noted in that report, it is not acceptable to mount stuff.
Ideally we will have to add cpio write support to busybox (and, but this
is not related, ar write support. Wrong list, though).