From: "J. Bruce Fields" <bfields@fieldses.org>
To: Ray Van Dolson <rvandolson-v48TKWNzwFw@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: pseudo root status?
Date: Fri, 19 Feb 2010 23:45:08 -0500 [thread overview]
Message-ID: <20100220044508.GA3689@fieldses.org> (raw)
In-Reply-To: <20100219190049.GA32080-v48TKWNzwFw@public.gmane.org>
On Fri, Feb 19, 2010 at 11:00:49AM -0800, Ray Van Dolson wrote:
> What is the status of the dynamic pseudo root support in nfs-utils? I
> see in commit b25694320f2bdd79de82f2003209b8229eafff36 mention of a way
> to define an export with a pseudo root, but I cloned Steve's latest git
> tree of nfs-utils and am not seeing much about pseudo root support at
> all.
>
> The 1.2.2 announcement message seems to include a blurb about it --
> does this version have what I need?
With a recent kernel and nfs-utils, if you just omit "fsid=0" from your
export file then NFSv4 clients should see the same paths as v2/v3
clients.
--b.
next prev parent reply other threads:[~2010-02-20 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 19:00 pseudo root status? Ray Van Dolson
[not found] ` <20100219190049.GA32080-v48TKWNzwFw@public.gmane.org>
2010-02-20 4:45 ` J. Bruce Fields [this message]
2010-02-23 17:57 ` Steve Dickson
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=20100220044508.GA3689@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rvandolson-v48TKWNzwFw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.