From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] cannot log to my build root
Date: Tue, 14 Dec 2010 15:05:20 +0100 [thread overview]
Message-ID: <20101214150520.253b9bae@surf> (raw)
In-Reply-To: <AANLkTi=GjsSptGonZv0S+BqCgYZZYoTOC=K+mTYpLrSd@mail.gmail.com>
On Tue, 14 Dec 2010 15:39:45 +0200
Diego Iastrubni <diegoiast@gmail.com> wrote:
> Nope. In my original case /dev/tty was not a char device (a null file
> instead). Creating these files fixed the problem:
This is because you are using the output/target/ directory, but you
should *not* do this. From the Buildroot documentation:
?
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.
?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-12-14 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 13:06 [Buildroot] cannot log to my build root Diego Iastrubni
2010-12-14 13:25 ` Thomas Petazzoni
2010-12-14 13:39 ` Diego Iastrubni
2010-12-14 14:05 ` Thomas Petazzoni [this message]
2010-12-14 14:38 ` Diego Iastrubni
2010-12-14 14:42 ` Thomas Petazzoni
2010-12-14 14:54 ` Diego Iastrubni
2010-12-14 15:05 ` Thomas Petazzoni
2010-12-14 15:28 ` Diego Iastrubni
2010-12-14 15:37 ` Thomas Petazzoni
2010-12-14 15:56 ` Diego Iastrubni
2010-12-14 16:00 ` Thomas Petazzoni
2010-12-14 15:50 ` William Wagner
2010-12-14 16:00 ` 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=20101214150520.253b9bae@surf \
--to=thomas.petazzoni@free-electrons.com \
--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