On Nov 14, 2012, at 6:12 PM, "Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx> 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@xxxxxxxxxx> wrote: >> >>>> -----Original Message----- >>>> From: linux-nfs-owner@xxxxxxxxxxxxxxx [mailto:linux-nfs- >>>> owner@xxxxxxxxxxxxxxx] On Behalf Of Chuck Lever >>>> Sent: Wednesday, November 14, 2012 5:39 PM >>>> To: linux-nfs@xxxxxxxxxxxxxxx >>>> Subject: [PATCH] nfs(5): Document the minorversion= mount option >>>> >>>> Signed-off-by: Chuck Lever <chuck.lever@xxxxxxxxxx> >>>> --- >>>> >>>> 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... ...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. 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. -- Chuck Lever chuck[dot]lever[at]oracle[dot]com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
