From: Chuck Lever Date: Mon, 29 Sep 2008 11:52:40 +0000 (-0400) Subject: nfs(5): Replace the term "netid" in mount option descriptions X-Git-Tag: nfs-utils-1-1-4~9 X-Git-Url: https://git.decadent.org.uk/gitweb/?p=nfs-utils.git;a=commitdiff_plain;h=8f1abb8ab1f7afcb9c2c0c094255d7e438b57b09;hp=8f1abb8ab1f7afcb9c2c0c094255d7e438b57b09 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 Cc: Mike Eisler Signed-off-by: Steve Dickson ---