Path: utzoo!attcan!uunet!mcvax!enea!maxim!prc From: prc@maxim.ERBE.SE (Robert Claeson) Newsgroups: comp.dcom.lans Subject: Re: NFS vs RFS Message-ID: <463@maxim.ERBE.SE> Date: 21 Jan 89 11:14:36 GMT References: <9018@cit-vax.Caltech.Edu> <7387@chinet.chi.il.us> Organization: ERBE DATA AB Lines: 39 In article , hedrick@geneva.rutgers.edu (Charles Hedrick) writes: > - if you open /dev/tty1 on another machine over RFS and cat to it, > it comes out on the remote machine's tty1. If you do this > under Sun's NFS, it comes out of tty1 on your own machine. Sun's > behavior is right for a protocol intended to support > diskless machines. My /dev directory, like all the rest > of my disk, is on my file server. I want to treat my > file server as if it were my own disk. When I open > /dev/tty, it want *my* /dev/tty, not the server's. Right, but what if you mount another workstation's or server's /dev as, say, /net/server/dev (where 'server' is the name of the other machine) and cat to it under the intention that something should come out on a printer connected to the other machine? Where does the output go? > - the NFS protocol itself doesn't include file locking. However > Sun has a related protocol that does do locking. Sun's > systems are intended to meet the full SVID, including > locking. There has been a history of bugs in file locking, > and it's not clear to me that even now it is totally bug > free, but this isn't a protocol issue: the protocol support > is present. The NFS locking protocol doesn't support the SVID's mandatory locking, but only the advisory locking. I guess it will be hard to implement mandatory locking in a stateless environment like NFS. () -- Robert Claeson, ERBE DATA AB, P.O. Box 77, S-175 22 Jarfalla, Sweden "No problems." -- Alf Tel: +46 758-202 50 EUnet: rclaeson@ERBE.SE uucp: uunet!erbe.se!rclaeson Fax: +46 758-197 20 Internet: rclaeson@ERBE.SE BITNET: rclaeson@ERBE.SE