Xref: utzoo comp.mail.misc:5244 comp.protocols.nfs:2180 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!convex!thurlow From: thurlow@convex.com (Robert Thurlow) Newsgroups: comp.mail.misc,comp.protocols.nfs Subject: Re: Symlink locking considered useless over NFS Message-ID: Date: 19 Apr 91 20:31:18 GMT References: <2800BA22.1CAE@tct.com> <1991Apr09.160512.1300@chinet.chi.il.us> <3064@cirrusl.UUCP> <280EE8A1.30D@tct.com> Sender: newsadm@convex.com (news access account) Organization: Convex Computer Corporation, Richardson, Tx. Lines: 19 Nntp-Posting-Host: dhostwo.convex.com In <280EE8A1.30D@tct.com> chip@tct.com (Chip Salzenberg) writes: >NFS's statelessness is supposed to be a feature. Well, as far as I'm >concerned, the designers of NFS can go take a flying leap, and they >can take their stateless protocol with them. C'mon Chip, flame in the right direction. The lack of support for O_EXCL in the create operation of NFS isn't a feature of statelessness, it's just a simple-minded protocol bug. If Sun would get off its cans and tell us the way a new protocol revision carried this information, all of us vendors could add support in ten minutes. But you can go ahead and flame Sun for the protocol bug and the time they've let go by on addressing it. Rob T -- Rob Thurlow, thurlow@convex.com An employee and not a spokesman for Convex Computer Corp., Dallas, TX