Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Failing NFS root mount
Date: Wed, 23 Apr 2008 00:07:27 +1000	[thread overview]
Message-ID: <20080422140727.GA32518@cloud.net.au> (raw)
In-Reply-To: <067701c8a475$2df6d860$ad289e86@LPSC0173W>

On Tue, Apr 22, 2008 at 02:34:08PM +0200, Guillaume Dargaud wrote:
> [    4.389172] VFS: Mounted root (nfs filesystem).
> [    4.392920] Freeing unused kernel memory: 76k init
> 
> And then it hangs.
> If I boot from /dev/xsa2, it then carries on with:

> A few additional hints that may be related (but then again, they may not):
> If I log from the local partition, I can mount the remote root by NFS fine, 
> for instance:
> 
> # mount -t nfs 
> 192.168.1.185:/home/guinevere/Min_UartLite_NetLite_Ace/buildroot/project_build_powerpc/genepy/root 
> /mount
> 
> And then manipulate files both ways fine.
> 
> But if I try to chroot /mount while being in bash (an independant 
> executable) I get an endless loop:

An excellent test. However, fairly obviously I think, if the shell
doesn't start in the chroot it's not going to start in a direct boot
either. So you need to figure out why.

> If I'm using ash (linked to busybox), then I can chroot okay (problems with 
> /proc but I can run executables).

What if you boot the system in that configuration?

You will need to mount /proc in the chroot too btw, and maybe /tmp and
/dev/pts too depending on what you run in there.

If your target is an embedded system, then busybox's ash is a much
better choice than bloatware bash anyway.

> Question: if booting off NFS, do I need to change the /etc/fstab ?
> /dev/root       /              ext2     rw,noauto         0      1

I don't think you ever need to list /dev/root in the fstab.. the kernel
certainly isn't using it to mount the root and I don't think anything
else is either.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  parent reply	other threads:[~2008-04-22 14:07 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 [this message]
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

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=20080422140727.GA32518@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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