Network File System - Typical Implementation

Typical Implementation

This section does not cite any references or sources.

Assuming a Unix-style scenario in which one machine (the client) requires access to data stored on another machine (the NFS server):

  1. The server implements NFS daemon processes (running by default as nfsd) in order to make its data generically available to clients.
  2. The server administrator determines what to make available, exporting the names and parameters of directories (typically using the /etc/exports configuration file and the exportfs command).
  3. The server security-administration ensures that it can recognize and approve validated clients.
  4. The server network configuration ensures that appropriate clients can negotiate with it through any firewall system.
  5. The client machine requests access to exported data, typically by issuing a mount command. (The client asks the server (rpcbind) which port the NFS server is using, the client connects to the NFS server (nfsd), nfsd passes the request to mountd)
  6. If all goes well, users on the client machine can then view and interact with mounted filesystems on the server within the parameters permitted.

Note that automation of the NFS mounting process may take place — perhaps using /etc/fstab and/or automounting facilities.

Read more about this topic:  Network File System

Famous quotes containing the word typical:

    “A building is akin to dogma; it is insolent, like dogma. Whether or no it is permanent, it claims permanence, like a dogma. People ask why we have no typical architecture of the modern world, like impressionism in painting. Surely it is obviously because we have not enough dogmas; we cannot bear to see anything in the sky that is solid and enduring, anything in the sky that does not change like the clouds of the sky.”
    —Gilbert Keith Chesterton (1874–1936)