NFS is a distributed file system service that can be used to share resources (files or directories) from one system, typically a server, with other systems on the network. For example, you might want to share third-party applications or source files with users on other systems.
NFS makes the actual physical location of the resource irrelevant to the user. Instead of placing copies of commonly used files on every system, NFS allows you to place one copy on one system's disk and let all other systems access it from the network. Under NFS, remote files are virtually indistinguishable from local files.
For more information, see Managing Network File Systems in Oracle Solaris 11.2 .
A system becomes an NFS server if it has resources to share on the network. A server keeps a list of currently shared resources and their access restrictions (such as read/write or read-only access).
When you share a resource, you make it available for mounting by remote systems.
You can share a resource in these ways:
Create a ZFS share by setting the ZFS share.nfs property. For example:
# zfs set share.nfs=on tank/home
Create a legacy share by using the share command.
# share -F nfs /ufsfs
For a complete description of NFS, see Managing Network File Systems in Oracle Solaris 11.2 .
Oracle's implementation of the NFS version 4 distributed file access protocol is included in the Oracle Solaris release.
NFS version 4 integrates file access, file locking, and mount protocols into a single, unified protocol to ease traversal through a firewall and improve security. The Oracle Solaris implementation of NFS version 4 is fully integrated with Kerberos V5, also known as SEAM, thus providing authentication, integrity, and privacy. NFS version 4 also enables the negotiation of security flavors to be used between the client and the server. With NFS version 4, a server can offer different security flavors for different file systems.
For more information about NFS Version 4 features, see Managing Network File Systems in Oracle Solaris 11.2 .