[PATCH] Re: docs/71782: mount_nfs man page is a bit out of date

[Kevin D. Kinsey, DaleCo, S.P.]

Chris Pepper wrote:

>The following reply was made to PR docs/71782; it has been noted by GNATS.
>
>From: Chris Pepper <pepper at reppep.com>
>To: FreeBSD-gnats-submit at FreeBSD.org, Guy Harris <guy at alum.mit.edu>
>Cc: freebsd-gnats-submit at FreeBSD.org
>Subject: Re: docs/71782: mount_nfs man page is a bit out of date
>Date: Sun, 19 Sep 2004 22:55:39 -0400
>
> At 12:15 AM +0000 2004/09/16, Guy Harris wrote:
> >  >Number:         71782
> >>Category:       docs
> >  >Synopsis:       mount_nfs man page is a bit out of date
> 
> >  >Description:
> >The mount_nfs man page claims that NFS-over-TCP is mainly a BSD thing:
> >
> >      -T      Use TCP transport instead of UDP.  This is recommended for
> >              servers that are not on the same LAN cable as the client.  (NB:
> >              This is NOT supported by most non-BSD servers.)
> >
> >and
> >
> >BUGS
> >      Due to the way that Sun RPC is implemented on top of UDP (unreliable
> >      datagram) transport, tuning such mounts is really a black art that can
> >      only be expected to have limited success.  For clients mounting servers
> >      that are not on the same LAN cable or that tend to be overloaded, TCP
> >      transport is strongly recommended, but unfortunately this is restricted
> >      to mostly 4.4BSD servers.
> 
> 	Further, all three occurrences of 'cable' should be 
> 'segment', as most of us are using network segments or subnets that 
> involve multiple cables (via hubs or switches). One cable per segment 
> (thicknet) is an anachronism.
> 
> 
> 						Chris
>  
>

OK, blast from the past, and not a total rewrite,
but how does this look to you guys?  Maybe we
can mark this off the list?

--------------------------------------------------------------------------------------------------------------------

--- mount_nfs.8.orig    Wed Oct 20 00:36:05 2004
+++ mount_nfs.8 Mon Dec 13 19:39:44 2004
@@ -141,9 +141,9 @@
 There is a 60 second delay between each attempt.
 .It Fl T
 Use TCP transport instead of UDP.
-This is recommended for servers that are not on the same LAN cable as
+This is recommended for servers that are not on the same physical 
network as
 the client.
-(NB: This is NOT supported by most
+(NB: This is NOT supported by most older
 .No non- Ns Bx
 servers.)
 .It Fl U
@@ -340,10 +340,7 @@
 .Sh BUGS
 Due to the way that Sun RPC is implemented on top of UDP (unreliable 
datagram)
 transport, tuning such mounts is really a black art that can only be 
expected
-to have limited success.
-For clients mounting servers that are not on the same
-LAN cable or that tend to be overloaded,
-TCP transport is strongly recommended,
-but unfortunately this is restricted to mostly
-.Bx 4.4
-servers.
+to have limited success. For clients mounting servers that are not on 
the same
+LAN segment or that tend to be overloaded, TCP transport is strongly
+recommended, but this is not supported by older,
+.No non- Ns Bx 4.4 servers.

-----------------------------------------------------------------------------------------------------------------

Kevin Kinsey