Unified I/O namespace: what's the point?
Peter da Silva
peter at ficc.ferranti.com
Fri Oct 12 10:26:19 AEST 1990
Submitted-by: peter at ficc.ferranti.com (Peter da Silva)
In article <13441 at cs.utexas.edu> brnstnd at kramden.acf.nyu.edu (Dan Bernstein) writes:
> In article <13392 at cs.utexas.edu> chip at tct.uucp (Chip Salzenberg) writes:
> > It is true that interactive use of UNIX, especially by programmers,
> > puts a lot of emphasis on the shell interface. If such an environment
> > were all there were to Unix, then Dan's fd-centric view of the world
> > could possibly be useful.
> The success of UNIX has proven how useful this ``fd-centric'' view is.
Not at all. You can equally argue that it proves how useful the "unified
name space" view is, because *that* is another of the features that marks
UNIX as something new. Or that it proves the "filter" concept, or any of
the other things that *as a whole* go to making UNIX what it is.
UNIX is synergy.
> This is also unfounded. My TCP connectors provide a counterexample to
> your hypothesis (that the shell must handle everything and hence be
> recompiled) and your conclusion (that fd-centric UNIX doesn't work).
> Any programming problem can be solved by adding a level of indirection.
OK, how do you put your TCP connectors into /etc/inittab as terminal
types? Or into /usr/brnstnd/.mailrc as mailbox names? Or into any other
program that expects filenames in configuration scripts (remember, not
all scripts are shell scripts).
> A unified namespace has several great disadvantages: 1. It provides a
> competing abstraction with file descriptors,
No, it adds a complementary abstraction to file descriptors. In fact, a
unified name space and file descriptors together form an abstraction that
is at the heart of UNIX: everything is a file. A file has two states: passive,
as a file name; and active, as a file descriptor.
> This will result in a confused system, where some features are available
> only under one abstraction or the other.
Which is what you seem to be advocating.
> A unified namespace has not been tested on
> a large scale in the real world, and hence is an inappropriate object of
> standardization at this time.
I would like to suggest that UNIX itself proves the success of a unified
namespace.
--
Peter da Silva. `-_-'
+1 713 274 5180. 'U`
peter at ferranti.com
Volume-Number: Volume 21, Number 200
More information about the Comp.std.unix
mailing list