From: Steve Dickson <SteveD@redhat.com>
To: Dax Kelson <dkelson@gurulabs.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: When did NFSv4 behavior change occur?
Date: Mon, 14 Mar 2011 13:23:11 -0400 [thread overview]
Message-ID: <4D7E4EFF.9060302@RedHat.com> (raw)
In-Reply-To: <1300120256.3600.19.camel@mentorng>
On 03/14/2011 12:30 PM, Dax Kelson wrote:
> In a quest to update our documentation, could someone please answer this
> question?
>
> What kernel version did the change occur where all the entries
> in /etc/exports are shared as v4 (in addition to v2 and v3) as well as
> the automatic psuedo-root creation if fsid=0 not exist?
kernel-2.6.32.
>
> Or maybe it was a combo of kernel version and nfs-utils version??
nfs-utils-1.2.2
steved.
>
> Dax Kelson
> Guru Labs
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-14 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 16:30 When did NFSv4 behavior change occur? Dax Kelson
2011-03-14 17:23 ` Steve Dickson [this message]
2011-03-15 21:30 ` J. Bruce Fields
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=4D7E4EFF.9060302@RedHat.com \
--to=steved@redhat.com \
--cc=dkelson@gurulabs.com \
--cc=linux-nfs@vger.kernel.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).