From: Jason Wessel <jason.wessel@windriver.com>
To: Saul Wold <saul.wold@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Allow user mode NFS server to run without rpcbind / portmap
Date: Mon, 10 Oct 2011 06:39:10 -0500 [thread overview]
Message-ID: <4E92D95E.3080400@windriver.com> (raw)
In-Reply-To: <4E927CD9.2040505@intel.com>
On 10/10/2011 12:04 AM, Saul Wold wrote:
> On 10/05/2011 11:43 AM, Jason Wessel wrote:
>>> From the 2.6.39 linux kernel and up it is possible to use
>> and nfsroot mount without the need to talk to an RPC info
>> server as long as the port numbers for mountd and nfsd
>> are known in advance.
>>
>> This patch updates the qemu startup scripts and the
>> user mode NFS server to have the ability to start
>> without the need to use rpcbind or portmap services.
>>
> Jason,
>
> I have not fully tested this yet, but if someone has rpcbind and/or
> portmap services are running, what affect will this patch have?
>
It works the same way it did before. Mountd and nfsd will register with rpcbind / portmap.
All that was done is to use a fall back to not register if the registration service is either denied or unavailable.
Jason.
next prev parent reply other threads:[~2011-10-10 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 18:43 [PATCH] Allow user mode NFS server to run without rpcbind / portmap Jason Wessel
2011-10-10 5:04 ` Saul Wold
2011-10-10 9:14 ` Richard Purdie
2011-10-10 11:39 ` Jason Wessel [this message]
2011-10-10 9:17 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2011-10-05 15:26 Jason Wessel
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=4E92D95E.3080400@windriver.com \
--to=jason.wessel@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.com \
/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