Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Failing NFS root mount (SOLVED)
Date: Wed, 23 Apr 2008 12:10:12 +0200	[thread overview]
Message-ID: <8763u8khkr.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <076001c8a527$0105e410$ad289e86@LPSC0173W> (Guillaume Dargaud's message of "Wed\, 23 Apr 2008 11\:47\:06 +0200")

>>>>> "Guillaume" == Guillaume Dargaud <dargaud@lpsc.in2p3.fr> writes:

 Guillaume> In retrospect that makes a lot of sense... (but then
 Guillaume> again, so do many things in life).

;)

 Guillaume> I was exporting with NFS the
 Guillaume> project_build_powerpc/genepy/root directory to mount as
 Guillaume> root. And that failed.

Ah yes, you are not supposed to do that. Instead enable tarball
creation under target options and untar that file uner your nfsroot
as root to get the proper permissions/devices.

See the 'Improper device nodes' thread on the list for details.

 Guillaume> But then if do:
 Guillaume> mount -o loop binaries/genepy/rootfs.powerpc.ext2 /media/loop/
 Guillaume> And export /media/loop instead, I can boot fine !!!

That's an option as well, but the tarball is handier.

 Guillaume> Doing a diff between the two dirs reveals that for
 Guillaume> instance the devices are normal files in the project
 Guillaume> directory...

Yes. This is handled by fakeroot so you can compile as non-root.

 >> Well, you'll need to unpack the tarball as root in order to create the
 >> device nodes and get the permissions right on stuff like /etc/passwd -
 >> If you do that, you shouldn't need to do any additional chown.

 Guillaume> I saw your reply right after solving it and that confirms it...

 Guillaume> Thanks to all who contributed.

You're welcome.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2008-04-23 10:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 12:34 [Buildroot] Failing NFS root mount Guillaume Dargaud
2008-04-22 13:38 ` sjhill at realitydiluted.com
2008-04-23  8:06   ` Guillaume Dargaud
2008-04-22 13:40 ` Peter Korsgaard
2008-04-22 14:07 ` Hamish Moffatt
2008-04-23  8:56   ` Guillaume Dargaud
2008-04-23  9:18     ` Peter Korsgaard
2008-04-23  9:47       ` [Buildroot] Failing NFS root mount (SOLVED) Guillaume Dargaud
2008-04-23 10:10         ` 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=8763u8khkr.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