Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] /dev nodes files
Date: Sun, 7 Jun 2009 20:48:43 +0200	[thread overview]
Message-ID: <20090607184843.GK26148@buzzloop.caiaq.de> (raw)

This has been discussed before, but I don't know if there was any
result, so I'm asking again.

After each build, the ixnodes in project_build_arm/uclibc/root/dev are
regular files rather than inodes, which prevents users from exporting
that directory directly as NFS root. Most people run custom scripts to
fix that, but I wonder whether there is any change to get that fixed in
BR2 directly.

The problem is that mknod can't create the nodes when not run as root,
and fakeroot doesn't help much in this case. Would it be an option to

 a) move the invocation of makedevs from target/*/*mk to some higher
    level. Actually, all fs deployment targets do the same thing, and
    that could be simplified.
 b) Let users choose whether to use 'fakeroot' or 'sudo' to create the
    inodes. The latter would need some augmented system priviledges, but
    as an option, that shouldn't harm.

Any oppinion about such an approach?

Daniel

             reply	other threads:[~2009-06-07 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-07 18:48 Daniel Mack [this message]
2009-06-07 18:53 ` [Buildroot] /dev nodes files Peter Korsgaard
2009-06-08 11:41   ` Daniel Mack

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=20090607184843.GK26148@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --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