From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: steved@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] nfs(5): Replace the term "netid" in mount option descriptions
Date: Tue, 23 Sep 2008 12:30:29 -0400 [thread overview]
Message-ID: <RTPCLUEXC1-PRDC8wSA000000ca@RTPMVEXC1-PRD.hq.netapp.com> (raw)
In-Reply-To: <20080923161636.5119.54434.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
To be pedantic, identifiying this field as a "prot" may be just as
misleading. For example "rdma" (which isn't mentioned btw ;-) )
can employ tcp - iWARP adapters do this.
I think instead that the proto= field simply names the "transport"
rather than "netid" or "prot". Also, I think "prot" is much too easily
mistaken for "port".
So I suggest changing the example to "proto=transport", and deleting
the word "protocol" in the text, simply leaving "the transport used by
NFS to transmit..."
Tom.
At 12:16 PM 9/23/2008, Chuck Lever wrote:
>Mike Eisler noted that the use of the term "netid" in the descriptions
>of the "proto=" option is not appropriate, since Linux does not allow
>"udp6" or "tcp6".
>
>Remove the term "netid" from nfs(5).
>
>Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
>---
>
> utils/mount/nfs.man | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
>
>diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
>index 0fc5079..b1037a8 100644
>--- a/utils/mount/nfs.man
>+++ b/utils/mount/nfs.man
>@@ -411,10 +411,10 @@ for mounting the
> .B nfs
> file system type.
> .TP 1.5i
>-.BI proto= netid
>+.BI proto= prot
> The transport protocol used by the NFS client
> to transmit requests to the NFS server for this mount point.
>-.I netid
>+.I prot
> can be either
> .B udp
> or
>@@ -489,11 +489,11 @@ or the server's mountd service is not available
>on the advertised port.
> This option can be used when mounting an NFS server
> through a firewall that blocks the rpcbind protocol.
> .TP 1.5i
>-.BI mountproto= netid
>+.BI mountproto= prot
> The transport protocol used by the NFS client
> to transmit requests to the NFS server's mountd service when performing
> this mount request, and when later unmounting this mount point.
>-.I netid
>+.I prot
> can be either
> .B udp
> or
>@@ -638,10 +638,10 @@ for mounting the
> .B nfs4
> file system type.
> .TP 1.5i
>-.BI proto= netid
>+.BI proto= prot
> The transport protocol used by the NFS client
> to transmit requests to the NFS server for this mount point.
>-.I netid
>+.I prot
> can be either
> .B udp
> or
>
>--
>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:[~2008-09-23 16:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 16:16 [PATCH 0/2] nfs(5) updates Chuck Lever
[not found] ` <20080923161322.5119.20872.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-23 16:16 ` [PATCH 1/2] nfs(5): Replace the term "netid" in mount option descriptions Chuck Lever
2008-09-23 16:16 ` [PATCH 2/2] nfs(5): Clarify behavior of the mountproto= and proto= options Chuck Lever
[not found] ` <20080923161636.5119.54434.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-23 16:30 ` Talpey, Thomas [this message]
[not found] ` <RTPCLUEXC1-PRDC8wSA000000ca-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 16:46 ` [PATCH 1/2] nfs(5): Replace the term "netid" in mount option descriptions Chuck Lever
2008-09-23 16:56 ` Trond Myklebust
2008-09-23 17:11 ` Chuck Lever
[not found] ` <76bd70e30809231011g5ed0cd11o6ccc06ab85f1a96c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[not found] ` <76bd70e30809231011g5ed0cd11o6ccc06ab85f1a96c-JsoAwUIsXouhRSP0FMvGiw@public.gmane.org m>
2008-09-23 19:04 ` Talpey, Thomas
[not found] ` <RTPCLUEXC1-PRDFRaqb000000d0-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 19:55 ` Chuck Lever
2008-09-29 11:37 ` Steve Dickson
[not found] ` <20080923161641.5119.37034.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-23 16:32 ` [PATCH 2/2] nfs(5): Clarify behavior of the mountproto= and proto= options Talpey, Thomas
[not found] ` <RTPCLUEXC1-PRD77bie000000cb-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 16:47 ` Chuck Lever
2008-09-23 16:41 ` Talpey, Thomas
[not found] ` <RTPCLUEXC1-PRDSzbAU000000cd-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 16:55 ` Chuck Lever
2008-09-29 11:38 ` 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=RTPCLUEXC1-PRDC8wSA000000ca@RTPMVEXC1-PRD.hq.netapp.com \
--to=thomas.talpey@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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