[Buildroot] No response after "Freeing init memory"
Zdeněk Materna
zdenek.materna at gmail.com
Wed Feb 23 15:54:33 UTC 2011
I promise that I will read FAQs more carefully :-) Thanks for patience! Now
I'm able to login and work.
Best regards,
Zdenek Materna
2011/2/23 Peter Korsgaard <jacmet at uclibc.org>
> >>>>> "Zdeněk" == Zdeněk Materna <zdenek.materna at gmail.com> writes:
>
> Zdeněk> Ouch, my mistake! All files in /dev are plain text... I have to
> Zdeněk> mount ext2 rootfs or untar rootfs from output/images on my
> Zdeněk> laptop, than share this over nfs like rootfs for my
> Zdeněk> board... I'm correct?
>
> Yes - Like it says in the documentation:
>
> http://buildroot.net/buildroot.html#using
>
> * target/ which contains almost the complete root filesystem for the
> target: everything needed is present except the device files in /dev/
> (Buildroot can't create them because Buildroot doesn't run as root and
> doesn't want to run as root). Therefore, this directory should not be
> used on your target. Instead, you should use one of the images built in
> the images/ directory. If you need an extracted image of the root
> filesystem for booting over NFS, then use the tarball image generated in
> images/ and extract it as root.
>
> --
> Bye, Peter Korsgaard
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110223/e107071f/attachment-0002.html>
More information about the buildroot
mailing list