Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!sdd.hp.com!ucsd!ucbvax!usenix!std-unix
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.unix
Subject: Re: Standards Update, IEEE 1003.4: Real-time Extensions
Message-ID: <491@usenix.ORG>
Date: 6 Sep 90 21:03:14 GMT
References: <448@usenix.ORG> <457@usenix.ORG> <488@usenix.ORG>
Sender: std-unix@usenix.ORG
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 15
Approved: jsq@usenix.org (Moderator, John Quarterman)
X-Submissions: std-unix@uunet.uu.net

From:  Doug Gwyn <gwyn@smoke.brl.mil>

In article <488@usenix.ORG> fouts@bozeman.bozeman.ingr (Martin Fouts) writes:
>I'm not sure which Unix you've been running for the past five or more
>years, but a lot of stuff doesn't live in the file system name space
>under various BSD derived systems, nor do the networking types believe
>it belongs there.

Excuse me, but the "networking types" I talk to believe that sockets
were a botch and that network connections definitely DO belong within
a uniform UNIX "file" name space.  Peter was quite right to note that
this is an essential feature of UNIX's design.  In fact there are UNIX
implementations that do this right, 4BSD is simply not among them yet.

Volume-Number: Volume 21, Number 85