Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!decvax!ucbvax!SEISMO.CSS.GOV!rick From: rick@SEISMO.CSS.GOV.UUCP Newsgroups: mod.protocols.tcp-ip Subject: Re: Need information on NFS Message-ID: <8612191855.AA12680@beno.CSS.GOV> Date: Fri, 19-Dec-86 13:55:44 EST Article-I.D.: beno.8612191855.AA12680 Posted: Fri Dec 19 13:55:44 1986 Date-Received: Sat, 20-Dec-86 06:24:47 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 18 Approved: tcp-ip@sri-nic.arpa By the way, several notes have talked about NFS "violating Unix semantics". The most common example is that file locking doesn't work across the network. It does now, in Sun release 3.2. This is only partially true. The system V lockf() IS supported by a lock daemon. However it does NOT support the 4.2bsd flock() file locking. Now since everything we do here is 4.2bsd compatible, not system 5, I maintain that file locking still doesn't work. We bought a 4.2bsd compatible system from Sun. We don't care what System 5 features they add. It still doesn't do forced apppend writes, nor permit accessing devices. That is something a good UNIX nfs would do. Those are clear violations of Unix semantics and not fixed (nor planned to be fixed as I understand it) ---rick