Differences between version 2 and predecessor to the previous major change of NetworkFileSystem.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Saturday, November 6, 2004 12:55:08 pm | by AristotlePagaltzis | Revert |
| Older page: | version 1 | Last edited on Thursday, November 14, 2002 7:20:54 pm | by PerryLorier | Revert |
@@ -1,7 +1,7 @@
+Created by SunMicrosystems, [NFS] is ''the'' Network FileSystem for [Unix]. [NFS] works on a RemoteProcedureCall system, translating all the calls you make on the local machine to open(2), read(2), write(2), close(2) etc to calls on the remote machine.
-Network File Systems: (See FileSystems)
+A nice thing about [NFS] is that it's stateless. Therefore, resource use on the server does not scale with the number of clients, and clients won't be affected as servers disappear and reappear. At least in theory.
-*
[NFS]
-*
[AFS
]
-*
[Coda
]
-*
[Intermezzo
]
+On the other hand, it lacks many advanced and even not so advanced features or newer networked FileSystems, such as disconnected operation. Its security model is simpleminded at best -- it maps [UID]s between machines, not even attempting to authenticate users. Locking on
[NFS] is notoriously unreliable. Performance is a mixed bag; many combinations of
[NFS
] server and client implementations lead to abysmal throughput. These and an assortment of other problems have led many a SysAdmin to expand the
[NFS
] acronym as Nightmare FileSystem.
+
+Because it is built on
[RPC], it does not use any single port and is therefor difficult for FireWall~s to handle. [Configuring NFS for firewall control | http://www.lowth.com/LinWiz/nfs_help.html
] steps you through the configuration process.
