diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2008-09-29 07:52:40 -0400 |
|---|---|---|
| committer | Steve Dickson <steved@redhat.com> | 2008-09-29 07:52:40 -0400 |
| commit | 8f1abb8ab1f7afcb9c2c0c094255d7e438b57b09 (patch) | |
| tree | 85124cc2ebcf3025a41f3eaa3e176fe380c1da4d /utils/mount/nfs.man | |
| parent | 4b3c476a3dd3a1fa7d6b1ff2a91406c30775208d (diff) | |
| download | nfs-utils-8f1abb8ab1f7afcb9c2c0c094255d7e438b57b09.tar.gz nfs-utils-8f1abb8ab1f7afcb9c2c0c094255d7e438b57b09.tar.xz nfs-utils-8f1abb8ab1f7afcb9c2c0c094255d7e438b57b09.zip | |
nfs(5): Replace the term "netid" in mount option descriptions
TI-RPC introduced the concept of "netid" which is a string that is
mapped to a set of transport capabilities via a netconfig database.
RPC services register a netid and bindaddr with their local rpcbind
daemon to advertise their ability to support particular transports.
Mike Eisler noted that the use of the term "netid" in nfs(5) is not
appropriate, since Linux does not treat the value of the proto= or
mountproto= options as a netid proper, but rather to select a
particular transport capability provided locally on the client.
The Linux NFS client currently uses a simple internal mapping between
these names and its own transport capabilities rather than using the
names as part of an rpcbind query, thus these strings are really not
netids. They are more akin to what TI-RPC calls "protocol names".
Remove the term "netid" from nfs(5) for now.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Cc: Mike Eisler <mike.eisler@netapp.com>
Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'utils/mount/nfs.man')
| -rw-r--r-- | utils/mount/nfs.man | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man index 319bf90..433e73a 100644 --- a/utils/mount/nfs.man +++ b/utils/mount/nfs.man @@ -412,14 +412,14 @@ for mounting the file system type. .TP 1.5i .BI proto= transport -The transport protocol used by the NFS client +The transport the NFS client uses to transmit requests to the NFS server for this mount point. -.I prot +.I transport can be either .B udp or .BR tcp . -Each transport protocol uses different default +Each transport uses different default .B retrans and .B timeo @@ -490,17 +490,17 @@ This option can be used when mounting an NFS server through a firewall that blocks the rpcbind protocol. .TP 1.5i .BI mountproto= transport -The transport protocol used by the NFS client +The transport the NFS client uses to transmit requests to the NFS server's mountd service when performing this mount request, and when later unmounting this mount point. -.I prot +.I transport can be either .B udp or .BR tcp . .IP This option can be used when mounting an NFS server -through a firewall that blocks a particular transport protocol. +through a firewall that blocks a particular transport. When used in combination with the .B proto option, different transports for mountd requests and NFS requests @@ -639,9 +639,9 @@ for mounting the file system type. .TP 1.5i .BI proto= transport -The transport protocol used by the NFS client +The transport the NFS client uses to transmit requests to the NFS server for this mount point. -.I prot +.I transport can be either .B udp or |