NFS Services Administrator's Guide (B.11.31.02) January 2008

• Mounting an NFS Version 2 filesystem using the UDP Transport
mount -o vers=2,proto=udp onc21:/var/mail /var/mail
In this example, the NFS client mounts the /var/mail directory from the NFS server,
onc21, using NFSv2 and the UDP protocol.
• Mounting an NFS filesystem using an NFS URL
mount nfs://onc31/Casey/mail /Casey/mail
In this example, the NFS client mounts the /Casey/mail directory from NFS server, onc31,
using the WebNFS protocol.
• Mounting an NFS filesystem by using a public file handle
mount -o public nfs://onc31/usr/%A0abc /Casey/Clay
If the public option or a URL is specified, the mount command attempts to connect to the
server using the public file handle. The daemonsrpcbind and mountd are not contacted.
In this example, the NFS client mounts /Casey/Clay directory by using a public file handle,
and an NFS URL that has a non 7-bit ASCII escape sequence from the NFS server, onc31.
• Mounting an NFS filesystem using native path
mount -o public onc31:C:Casey:test1 /Casey/test
A native path is a pathname that is interpreted according to conventions used on the native
operating system of the NFS server.
In this example, the NFS client mounts the /Casey/test directory using a native path and
a public file handle.
• Mounting a replicated set of NFS filesystems with same pathnames
mount -r onc21,onc23,onc25:/Casey/Clay /Casey/Clay
In this example, the NFS client mounts a single filesystem, /Casey/Clay that has been
replicated to a number of servers with the same pathnames. This enables the NFS client to
failover to either server onc21, onc23, or onc25 if the current server has become
unavailable.
• Mounting replicated set of NFS file systems with different pathnames
mount -r onc21:/Casey/Clay,onc23:/Var/Clay,nfs://srv-z/Clay /Casey/Clay
In this example, the NFS client mounts a replicated set of NFS file systems with different
pathnames.
Secure Mounting of Directories
The mount command enables you to specify the security mode for each NFS mount-point. This
allows the NFS client to request a specific security mode. However, if the specific mode does not
exist on the server, then the mount fails. Use the sec option to specify the security mode.
If sec is not specified in NFSv2, then the AUTH_SYS mode is used by default. If sec is not
specified in NFSv3, then the default action is for the NFS client to query the server about the
security mode to be used. The resulting security mode is negotiated between the NFS client and
server. For more information on the available security modes, see nfssec(5).
An Example for Securely Mounting a directory
In the following example, the NFS client forces the use of krb5 as the secure mode. The krb5
secure mode uses the Kerberos V5 protocol to authenticate users before granting access to the
shared filesystems. In this example, the NFS server, onc21, also supports the same secure mode.
mount -F nfs -o sec=krb5 onc21:/casey/nfs /casey/nfs
Configuring and Administering NFS Clients 43