In article <firstname.lastname@example.org>,
Scott Schwartz <email@example.com.NO-SPAM> wrote:
=>| Plan 9 (of beloved memory ) did pretty much the same thing.
=>And Inferno (c.f. comp.os.inferno, http://inferno.lucent.com/) does it
To clarify, I have no problem whatsoever having things live in
a common namespace; that is obviously a good thing. What I have
some objection to is calling everything in that namespace a file.
The traditional notion of a file, an organized collection of data,
seems unnatural for things like terminals, system control interfaces,
etc. If you can make these thing look like files from one angle,
that's fine, and probably useful, but it still isn't a file. Calling
something what is isn't is not helpful when looking at it in the
Gary D. Duzan
Humble Practitioner of the Computing Arts