Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: 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 10:17:19 +0100	[thread overview]
Message-ID: <1318238248.23801.7.camel@ted> (raw)
In-Reply-To: <1317840239-5290-1-git-send-email-jason.wessel@windriver.com>

On Wed, 2011-10-05 at 13:43 -0500, 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.
> 
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
> ---
>  .../023-no-rpc-register.patch                      |   34 ++++++++++++++++++++
>  .../unfs-server/unfs-server_2.1+2.2beta47.bb       |    3 +-
>  scripts/runqemu-export-rootfs                      |    4 ++-
>  scripts/runqemu-internal                           |   16 +++------
>  4 files changed, 44 insertions(+), 13 deletions(-)
>  create mode 100644 meta/recipes-devtools/unfs-server/unfs-server-2.1+2.2beta47/023-no-rpc-register.patch

Merged to master, thanks.

Richard




  parent reply	other threads:[~2011-10-10  9:23 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
2011-10-10  9:17 ` Richard Purdie [this message]
  -- 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=1318238248.23801.7.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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