Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] /dev files not being created correctly
Date: Wed, 15 Apr 2009 07:39:07 +0200	[thread overview]
Message-ID: <87eivua32c.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <204928.46075.qm@web43412.mail.sp1.yahoo.com> (Mark Fisher's message of "Tue\, 14 Apr 2009 06\:55\:14 -0700 \(PDT\)")

>>>>> "Mark" == Mark Fisher <fobs12@ymail.com> writes:

 Mark> Hi,

 Mark> I'm relatively new to buildroot and am using the 2009.02
 Mark> release of buildroot on a Fedora 9 platform and targeting an
 Mark> embedded device with an Intel Atom processor.
 
 Mark> When the root filesystem is built the types of the files are
 Mark> all set to plain text files. So for instance the /dev/console
 Mark> is not set to be a character device. This has already create
 Mark> problems when I try to boot because the console could not be
 Mark> opened. I manually fixed /dev/console and /dev/null. I'm still
 Mark> having trouble booting the image and also after a re-build my
 Mark> custom changes were lost.

You shouldn't use the project_build_arm/*/root directory to boot from
NFS. The /dev entries are normal files as we don't want to require
root rights while building. Instead create a tarball (target
filesystem options->tar the root filesystem) and extract that (found
under binaries/) as root on your nfs server.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2009-04-15  5:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 13:55 [Buildroot] /dev files not being created correctly Mark Fisher
2009-04-14 15:12 ` Bjørn Forsman
2009-04-15  5:39 ` Peter Korsgaard [this message]

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=87eivua32c.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