Unexpected NFS Effects

Bill Sommerfeld wesommer at athena.mit.edu
Fri Jun 30 12:00:44 AEST 1989


In article <1602 at munnari.oz.au> mwp at munnari (Michael Paddon) writes:

   The other point to remember is that NFS is a general protocol (not Unix
   specific). 

I find this hard to believe.  The documentation pays lip service to
this goal, but fall badly short of it in a number of places.  (That
line seems to be used as an excuse for not providing full UNIX
semantics).

*) The set of attributes associated with files corresponds exactly
(1:1) with the attributes used in UNIX, and there's no way to extend
the attributes passed around (that's not UNIX-specific?).

*) The protocol attempts to hide the fact that '/' is the path component
separator, except that '/' are passed "bare" in symlinks.

*) Access control must be inferred on the client from the
(UNIX-specific) file attributes provided by the server.  The server
gets to trump the client's decision, of course, but at that point it
may be too late.

There are others..

					- Bill
--



More information about the Comp.unix.wizards mailing list