NFS Services Administrator's Guide (5900-1632, August 2011)

Figure 4 NFS Mount of manpages
• Mounting a Home directory
mount -r -o nosuid broccoli:/home/broccoli /home/broccoli
mount -r -o nosuid cauliflower:/home/cauliflower /home/cauliflower
In this example, the NFS client mounts the home directories from NFS servers broccoli and
cauliflower . The nosuid option prevents programs with setuid permission from executing
on the local client.
Figure 5 illustrates this example.
Figure 5 NFS Mount of Home Directories
• 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 daemons rpcbind 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.
Configuring and Administering NFS Clients 37