-.TP
-.IR map_daemon
-This option turns on dynamic uid/gid mapping. Each uid in an NFS request
-will be translated to the equivalent server uid, and each uid in an
-NFS reply will be mapped the other way round. This option requires that
-.IR rpc.ugidd (8)
-runs on the client host. The default setting is
-.IR map_identity ,
-which leaves all uids untouched. The normal squash options apply regardless
-of whether dynamic mapping is requested or not.
-.TP
-.IR map_static
-This option enables static mapping. It specifies the name of the file
-that describes the uid/gid mapping, e.g.
-.IP
-.IR map_static=/etc/nfs/foobar.map
-.IP
-The file's format looks like this
-.IP
-.nf
-.ta +3i
-# Mapping for client foobar:
-# remote local
-uid 0-99 - # squash these
-uid 100-500 1000 # map 100-500 to 1000-1500
-gid 0-49 - # squash these
-gid 50-100 700 # map 50-100 to 700-750
-.fi
-.TP
-.IR map_nis
-This option enables NIS-based uid/gid mapping. For instance, when
-the server encounters the uid 123 on the server, it will obtain the
-login name associated with it, and contact the NFS client's NIS server
-to obtain the uid the client associates with the name.
-.IP
-In order to do this, the NFS server must know the client's NIS domain.
-This is specified as an argument to the
-.I map_nis
-options, e.g.
-.IP
-.I map_nis=foo.com
-.IP
-Note that it may not be sufficient to simply specify the NIS domain
-here; you may have to take additional actions before
-.I nfsd
-is actually able to contact the server. If your distribution uses
-the NYS library, you can specify one or more NIS servers for the
-client's domain in
-.IR /etc/yp.conf .
-If you are using a different NIS library, you may have to obtain a
-special
-.IR ypbind (8)
-daemon that can be configured via
-.IR yp.conf .
+'''.TP
+'''.IR map_daemon
+'''This option turns on dynamic uid/gid mapping. Each uid in an NFS request
+'''will be translated to the equivalent server uid, and each uid in an
+'''NFS reply will be mapped the other way round. This option requires that
+'''.IR rpc.ugidd (8)
+'''runs on the client host. The default setting is
+'''.IR map_identity ,
+'''which leaves all uids untouched. The normal squash options apply regardless
+'''of whether dynamic mapping is requested or not.
+'''.TP
+'''.IR map_static
+'''This option enables static mapping. It specifies the name of the file
+'''that describes the uid/gid mapping, e.g.
+'''.IP
+'''.IR map_static=/etc/nfs/foobar.map
+'''.IP
+'''The file's format looks like this
+'''.IP
+'''.nf
+'''.ta +3i
+'''# Mapping for client foobar:
+'''# remote local
+'''uid 0-99 - # squash these
+'''uid 100-500 1000 # map 100-500 to 1000-1400
+'''gid 0-49 - # squash these
+'''gid 50-100 700 # map 50-100 to 700-750
+'''.fi
+'''.TP
+'''.IR map_nis
+'''This option enables NIS-based uid/gid mapping. For instance, when
+'''the server encounters the uid 123 on the server, it will obtain the
+'''login name associated with it, and contact the NFS client's NIS server
+'''to obtain the uid the client associates with the name.
+'''.IP
+'''In order to do this, the NFS server must know the client's NIS domain.
+'''This is specified as an argument to the
+'''.I map_nis
+'''options, e.g.
+'''.IP
+'''.I map_nis=foo.com
+'''.IP
+'''Note that it may not be sufficient to simply specify the NIS domain
+'''here; you may have to take additional actions before
+'''.I nfsd
+'''is actually able to contact the server. If your distribution uses
+'''the NYS library, you can specify one or more NIS servers for the
+'''client's domain in
+'''.IR /etc/yp.conf .
+'''If you are using a different NIS library, you may have to obtain a
+'''special
+'''.IR ypbind (8)
+'''daemon that can be configured via
+'''.IR yp.conf .