From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfs(5): Document the minorversion= mount option
Date: Fri, 16 Nov 2012 08:39:01 -0500 [thread overview]
Message-ID: <50A641F5.3080403@RedHat.com> (raw)
In-Reply-To: <8CFA849C-DE85-41BB-8EEA-DBC9FF65FB6E@oracle.com>
Hey Chuck,
First of all, thanks for point this out...
On 14/11/12 18:37, Chuck Lever wrote:
>
> On Nov 14, 2012, at 6:12 PM, "Myklebust, Trond" <Trond.Myklebust@netapp.com> wrote:
>
>> On Wed, 2012-11-14 at 18:03 -0500, Chuck Lever wrote:
>>> On Nov 14, 2012, at 6:01 PM, "Myklebust, Trond" <Trond.Myklebust@netapp.com> wrote:
>>>
>>>>> -----Original Message-----
>>>>> From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs-
>>>>> owner@vger.kernel.org] On Behalf Of Chuck Lever
>>>>> Sent: Wednesday, November 14, 2012 5:39 PM
>>>>> To: linux-nfs@vger.kernel.org
>>>>> Subject: [PATCH] nfs(5): Document the minorversion= mount option
>>>>>
>>>>> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
>>>>> ---
>>>>>
>>>>> Our pals on the Solaris team recently noticed that the minorversion= option
>>>>> is not documented in nfs(5). This is a first take, just to start the conversation.
>>>>> I'm pretty sure I got the kernel version information wrong, for instance.
>>>>>
>>>>> Any other comments?
>>>>
>>>> You might want to note that it is deprecated in favour of the "vers=4.1" notation, and for that reason we might want to forgo documenting it altogether.
>>>
>>> OK. minorversion= is the only way to get NFSv4.1 on EL6-based distributions, isn't it?
>>
>> You didn't seem to be writing a manpage for the RHEL-6 distros: "Before
>> kernel 2.6.38, the minor version is always zero...". As far as I know,
>> RHEL-6 is still based on 2.6.32...
2.6.32 is where we made the branch. So it accurate to say RHEL6 is based
on 2.6.36, but in reality it absolutely not a straight 2.6.32 upstream
kernel due to all the backporting we do.
>
> ...for some very loose definition of "based on". One wonders how to document kernel versions in this instance. One way to fix this is to have RH patch their copy of nfs(5) privately, while upstream nfs-utils can handle this in some other way.
Yeah, We'll have to carry an private patch that updates the man page.
>
> However, search for "Parallel NFS" on this page:
>
> https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.2_Release_Notes/index.html
>
> This seems to me to count as public documentation of "minorversion=", and suggests that people are likely already using this formal API. I would hesitate to remove it in this instance.
>
If upstream wants to deprecate minorversion= than so be it... That will have
little effect on a RHEL release since we can't change the API like that...
steved.
next prev parent reply other threads:[~2012-11-16 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 22:39 [PATCH] nfs(5): Document the minorversion= mount option Chuck Lever
2012-11-14 23:01 ` Myklebust, Trond
2012-11-14 23:03 ` Chuck Lever
2012-11-14 23:12 ` Myklebust, Trond
2012-11-14 23:37 ` Chuck Lever
2012-11-16 13:39 ` Steve Dickson [this message]
2012-11-16 14:05 ` Chuck Lever
2012-11-16 14:12 ` 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=50A641F5.3080403@RedHat.com \
--to=steved@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=chuck.lever@oracle.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).