From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: linux-nfs@vger.kernel.org
Subject: [patch] fix description of nfsversion mount option
Date: Sat, 14 Aug 2010 16:53:38 +0200 [thread overview]
Message-ID: <4C66ADF2.9030700@inria.fr> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 614 bytes --]
Hello list.
Here is a first patch trying to update a little bit nfs-utils
documentation. I'd like also to change the constant opposition of 'nfs'
vs 'nfs4' filesystems in this man page, but I have no clue if the plan
is to remove 'nfs4' filesystem completly, or to keep for compatibility
purpose. In the first case, I'd just remove any occurence of it in the
man page, in the second case, I'm less sure about what to do.
Also, I really think NEWS and ChangeLOG files should be either dropped,
or merged and updated.
--
BOFH excuse #295:
The Token fell out of the ring. Call us when you find it.
[-- Attachment #1.2: 0001-fix-description-of-nfsversion-mount-option.patch --]
[-- Type: text/plain, Size: 1288 bytes --]
From b03afedc798ff96cab3d5b174ed620fd126abb71 Mon Sep 17 00:00:00 2001
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
Date: Sat, 14 Aug 2010 16:46:59 +0200
Subject: [PATCH] fix description of nfsversion mount option
---
utils/mount/nfs.man | 11 +++--------
1 files changed, 3 insertions(+), 8 deletions(-)
diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
index c64de5f..3806635 100644
--- a/utils/mount/nfs.man
+++ b/utils/mount/nfs.man
@@ -623,14 +623,9 @@ in such cases.
.TP 1.5i
.BI nfsvers= n
The NFS protocol version number used to contact the server's NFS service.
-The Linux client supports version 2 and version 3 of the NFS protocol
-when using the file system type
-.BR nfs .
-If the server does not support the requested version,
-the mount request fails.
-If this option is not specified, the client attempts to use version 3,
-but negotiates the NFS version with the server if version 3 support
-is not available.
+If the server does not support the requested version, the mount request fails.
+If this option is not specified, the client negociate a suitable version with
+the server, trying version 4 first, version 3 second, and version 2 last.
.TP 1.5i
.BI vers= n
This option is an alternative to the
--
1.7.2.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4251 bytes --]
next reply other threads:[~2010-08-14 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 14:53 Guillaume Rousse [this message]
2010-08-17 21:49 ` [patch] fix description of nfsversion mount option Steve Dickson
2010-08-28 16:58 ` Guillaume Rousse
2010-08-30 16:54 ` Chuck Lever
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=4C66ADF2.9030700@inria.fr \
--to=guillaume.rousse@inria.fr \
--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 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.