Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] dev nodes as regular files
Date: Tue, 7 Sep 2010 09:25:33 +0200	[thread overview]
Message-ID: <20100907092533.110fd587@surf> (raw)
In-Reply-To: <AANLkTikBSYh1WoKXAxVjEv4VvmBnXs-ac9p2f7iTWYOE@mail.gmail.com>

Hello Sergey,

On Tue, 7 Sep 2010 10:59:25 +0400
Sergey Naumov <sknaumov@gmail.com> wrote:

> All device nodes created as regular files with zero length, while
> mknod utility present.
> Does anybody know a reason of this behavior?

Where are you looking at ?

I think you're probably looking at output/target, which obviously does
not contain the correct device files. This is because root priviledges
are required to create device files, and we don't want Buildroot to do
anything as root (that's one of the feature of Buildroot).

Therefore, the device files are only present in the final
filesystem images (created in output/images), they are created using
the 'fakeroot' utility, which as it names says, allows to fake the fact
that we are root, for a particular set of operations.

Therefore, the directory/files in output/target are *NOT* the final
target filesystem. You must use one of the images generated in
output/images. The list of images generated in this directory is
configured using the "Target filesystem options -->" menu in
menuconfig/xconfig.

If you need any other detail, don't hesitate to ask!

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2010-09-07  7:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07  6:59 [Buildroot] dev nodes as regular files Sergey Naumov
2010-09-07  7:25 ` Thomas Petazzoni [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=20100907092533.110fd587@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