From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Failing NFS root mount
Date: Wed, 23 Apr 2008 11:18:55 +0200 [thread overview]
Message-ID: <87iqy9j5ds.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <06fe01c8a51f$e37d5470$ad289e86@LPSC0173W> (Guillaume Dargaud's message of "Wed\, 23 Apr 2008 10\:56\:10 +0200")
>>>>> "Guillaume" == Guillaume Dargaud <dargaud@lpsc.in2p3.fr> writes:
Hi,
Guillaume> Question: the exported nfs dir, must be "chown -R
Guillaume> root:root" beforehand, right ? If I don't do so, then I
Guillaume> can't do much with it, but I didn't see this fact stated
Guillaume> anywhere.
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.
>> Does it work with nfs over tcp? E.G. nfsroot=<ip>:<path>,tcp
Guillaume> Same thing.
Ok.
>> Does init=/bin/date or init=/bin/sh work?
Guillaume> Slightly different result:
Guillaume> [ 4.423251] Freeing unused kernel memory: 76k init
Guillaume> [ 4.700870] Kernel panic - not syncing: Attempted to kill init!
Guillaume> [ 4.705622] Rebooting in 180 seconds..
Ahh, so probably date gets to run just fine, but you just don't see
any output.
Do you have a /dev/ttyUL0 device node (c 204 187)? Are you running a
getty on it? (A ttyUL0::respawn:/sbin/getty -L ttyUL0 115200 vt100
line in /etc/inittab)
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-04-23 9:18 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 [this message]
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=87iqy9j5ds.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