From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] /dev nodes files
Date: Mon, 8 Jun 2009 13:41:51 +0200 [thread overview]
Message-ID: <20090608114151.GR26148@buzzloop.caiaq.de> (raw)
In-Reply-To: <874ouryix1.fsf@macbook.be.48ers.dk>
On Sun, Jun 07, 2009 at 08:53:46PM +0200, Peter Korsgaard wrote:
> Daniel> After each build, the ixnodes in project_build_arm/uclibc/root/dev are
> Daniel> regular files rather than inodes, which prevents users from exporting
> Daniel> that directory directly as NFS root. Most people run custom scripts to
> Daniel> fix that, but I wonder whether there is any change to get that fixed in
> Daniel> BR2 directly.
>
> Ehh, that's on purpose (E.G. so you don't need root permissions to
> build). Just select the tarball target and extract it on your nfs
> server.
>
> Daniel> Any oppinion about such an approach?
>
> What would this buy us that the tarball target doesn't give?
Ok, understood. Thanks :)
Daniel
prev parent reply other threads:[~2009-06-08 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 18:48 [Buildroot] /dev nodes files Daniel Mack
2009-06-07 18:53 ` Peter Korsgaard
2009-06-08 11:41 ` Daniel Mack [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=20090608114151.GR26148@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