Path: utzoo!attcan!uunet!usenix!jsq From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.std.unix Subject: Re: Standards Update, IEEE 1003.4: Real-time Extensions Message-ID: <551@usenix.ORG> Date: 27 Sep 90 17:14:30 GMT References: <541@usenix.ORG> <543@usenix.ORG> <544@usenix.ORG> Sender: jsq@usenix.ORG Organization: Teltronics/TCT, Sarasota, FL Lines: 15 Approved: jsq@usenix.org (Moderator, John Quarterman) X-Submissions: std-unix@uunet.uu.net Submitted-by: chip@tct.uucp (Chip Salzenberg) According to brnstnd@kramden.acf.nyu.edu (Dan Bernstein): >NFS (as it is currently implemented) shows what goes wrong when >reliability disappears. In a discussion of filesystem semantics, NFS is a straw man. Everyone knows it's a botch. If AFS and RFS don't convince one that a networked filesystem namespace can work well, then nothing will. -- Chip Salzenberg at Teltronics/TCT , Volume-Number: Volume 21, Number 139