Network File System: Difference between revisions

Revision as of 21:20, 21 October 2024

Revision as of 21:22, 21 October 2024

Line 85:

* [[OS/2]]<ref>{{cite web|url=https://ecsoft2.org/network-file-system-nfs-plugin-netdrive|access-date=2020-09-22|website=ecsoft2.org|title=NTFS plugin for NetDrive}}</ref>

* [[ArcaOS]]<ref>{{cite web|url=https://www.arcanoae.com/shop/netdrive-for-os2/|title=NetDrive for OS/2|access-date=2020-09-22|website=arcanoae.com}}</ref>

* [[Novell NetWare]],<ref name="NFSforNetWare">{{cite web|title=NFS Gateway for NetWare 6.5|url=https://www.novell.com/products/openenterpriseserver/features/nfs-gateway-for-netware65.html|website=www.novell.com|publisher=Novell|access-date=24 September 2016}}</ref> although the defultdefault networking protocol is [[NetWare Core Protocol]] (NCP)

* [[IBM i]],<ref name="OS/400-NFS">{{cite web|title=OS/400 Network File System Support|url=https://public.dhe.ibm.com/systems/power/docs/systemi/v5r4/en_US/sc415714.pdf|publisher=IBM|access-date=23 May 2024}}</ref> although the default networking protocol is OS/400 File Server (QFileSvr.400)

Line 91:

[[File:NfsPerformanceGraph.png|thumb|600px|center|NFS SPECsfs2008 performance comparison, as of 22 November 2013]]

=== Typical implementation ===

{{unreferenced section|date=February 2010}}

Assuming a Unix-style scenario in which one machine (the [[Client (computing)|client]]) needs access to data stored on another machine (the NFS [[Server (computing)|server]]):

# The server implements NFS [[Daemon (computer software)|daemon]] processes, running by default as <code>nfsd</code>, to make its data generically available to clients.

# The server administrator determines what to make available, exporting the names and parameters of [[Directory (file systems)|directories]], typically using the <code>/etc/exports</code> configuration file and the <code>exportfs</code> command.

# The server [[network security|security]]-administration ensures that it can recognize and approve validated clients.

# The server network configuration ensures that appropriate clients can negotiate with it through any [[Firewall (networking)|firewall]] system.

# The client machine requests access to exported data, typically by issuing a <code>mount</code> 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)

# If all goes well, users on the client machine can then view and interact with mounted [[filesystem]]s on the server within the parameters permitted.

Automation of the NFS mounting process may take place — perhaps using <code>/etc/fstab</code> or [[Berkeley Automounter|automounting]] facilities.

== Protocol development ==