From: Robin Gilks <robin.gilks@tait.co.nz>
To: linuxppc mail list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: kernel config & nfs (maybe!!)
Date: Wed, 17 Sep 2003 12:11:31 +1200 [thread overview]
Message-ID: <3F67A6B3.7010405@tait.co.nz> (raw)
In-Reply-To: <3F6778D0.1010700@tait.co.nz>
Never mind!!
Turned out to be the /dev directory in the host copy of the root fs
didn't have all the special files in it that it should have had so I was
unable to execute the init task once the root nfs mount was done.
Robin Gilks wrote:
>
> Greetings
>
> I might be missing something here with nfsroot, kernel config & the
> kernel command line but...
>
> When one does a "make oldconfig", is there a way to stop it asserting
> the lockd config if nfs is enabled? Its driving me nuts trying to do an
> automated build of a kernel that doesn't require a local rpc server to
> do the locking and since I want to boot with a nfsroot filesystem, I
> can't see how to get the -o nolock across the kernel command line.
>
--
Robin Gilks
Senior Design Engineer Phone: (+64)(3) 357 1569
Tait Electronics Fax : (+64)(3) 359 4632
PO Box 1645 Christchurch Email : robin.gilks@tait.co.nz
New Zealand
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-09-17 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 20:55 kernel config & nfs (maybe!!) Robin Gilks
2003-09-17 0:11 ` Robin Gilks [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=3F67A6B3.7010405@tait.co.nz \
--to=robin.gilks@tait.co.nz \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).