From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] No response after "Freeing init memory"
Date: Wed, 23 Feb 2011 16:23:18 +0100 [thread overview]
Message-ID: <87oc62yduh.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <AANLkTimf6Yvj1CSSwPT4Qg399_72ZOQhaR9tvPx_w+sM@mail.gmail.com> ("Zdeněk Materna"'s message of "Wed, 23 Feb 2011 12:00:00 +0100")
>>>>> "Zden?k" == Zden?k Materna <zdenek.materna@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 prev parent reply other threads:[~2011-02-23 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 20:53 [Buildroot] No response after "Freeing init memory" Zdeněk Materna
2011-02-21 20:57 ` Belisko Marek
2011-02-22 8:06 ` Zdeněk Materna
2011-02-22 18:25 ` Thomas Petazzoni
2011-02-22 19:04 ` ANDY KENNEDY
2011-02-23 10:50 ` Zdeněk Materna
2011-02-23 11:00 ` Zdeněk Materna
2011-02-23 15:23 ` Peter Korsgaard [this message]
2011-02-23 15:54 ` Zdeněk Materna
2011-02-23 16:38 ` ANDY KENNEDY
2011-02-23 17:05 ` Zdeněk Materna
2011-02-21 21:23 ` Charles Krinke
2011-02-21 21:27 ` Daniel Nyström
2011-02-21 22:21 ` Thomas Petazzoni
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=87oc62yduh.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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