1 The division of NFS between client and serverNFS Follows the Client server model, in which the server is the system that owns the file system resource and is configured to share it with other systems .An NFS-shareable resource is usually referred to as an exported file system. The client is the resource user .It uses the exported file system as if it were part of the local file system .To achieve this transparency, the client is said to mount the exported directory to the local file system.In Figure(2) , /efs is the exported directory on host netrix (the NFS server). To access that directory from client jade, it must be mounted first.To do that ,the administrator creates the /ifs directory to use as the mount directory and issues the appropriate mount command .Consecuently, to access the file budget.rpt from host jade, the user must specify /ifs/reports/budget.rpt as the path to that file. Figure 2 The relationship between the NFS server and client file systems. To transparently access the file budget.rpt from host jade, the user mounts the exported directory /efs on NFS server netrix and specifies / ifs/report/budget.rpt as the path to the command.3.1Architecture of NFS NFS is designed to give users high performance, transparent access to server file systems on global networks. Some of the most important design principles are summarized below: Transparent Access: Users and applications can access remote files as if they were local. They are not required to know whether the files reside on the local disk or on remote servers. Portability: NFS is machine and operating system independent. This allows it to be ported easily to multiple OS and hardware platforms from PCs to mainframes. Fast Recovery From Failure: NFS is designed to recover quickly from system failures and network problems, causing minimal disruption of service to users. Network Protocol Independence: NFS has the flexibility to run on multiple transp...
