From 0e9f14db1f3e0116051794ab16e6e313125576b2 Mon Sep 17 00:00:00 2001 From: rmacklem Date: Thu, 28 Apr 2011 00:20:35 +0000 Subject: Update man pages related to the change in default NFS client applied by r221124. I also deleted references to idmapd, since that daemon no longer exists. This is a content change. --- sbin/mount_nfs/mount_nfs.8 | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'sbin/mount_nfs') diff --git a/sbin/mount_nfs/mount_nfs.8 b/sbin/mount_nfs/mount_nfs.8 index 3933430..59d6cb4 100644 --- a/sbin/mount_nfs/mount_nfs.8 +++ b/sbin/mount_nfs/mount_nfs.8 @@ -28,7 +28,7 @@ .\" @(#)mount_nfs.8 8.3 (Berkeley) 3/29/95 .\" $FreeBSD$ .\" -.Dd July 28, 2009 +.Dd April 27, 2011 .Dt MOUNT_NFS 8 .Os .Sh NAME @@ -63,6 +63,12 @@ It implements the mount protocol as described in RFC 1094, Appendix A and .%T "NFS: Network File System Version 3 Protocol Specification" , Appendix I. .Pp +If the file system type is specified as ``oldnfs'', which implies this +command is run as ``mount_oldnfs'', then it forces use of the old NFS +client, which does not support the +.Cm nfsv4 +option. +.Pp By default, .Nm keeps retrying until the mount succeeds. @@ -163,10 +169,8 @@ Note that NFS version 2 has a file size limit of 2 gigabytes. Use the NFS Version 3 protocol. .It Cm nfsv4 Use the NFS Version 4 protocol. -This option will force the mount to use the experimental nfs subsystem and +This option will force the mount to use TCP transport. -To use the experimental nfs subsystem for nfsv2 and nfsv3 mounts, you -must specify the ``newnfs'' file system type instead of ``nfs''. .It Cm noconn For UDP mount points, do not do a .Xr connect 2 . -- cgit v1.1