From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <0b8a3f246291f2ea2597b61df48d80aa@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dir tree Qs
From: Charles Forsyth <forsyth@terzarima.net>
Date: Thu, 17 Aug 2006 20:29:51 +0100
In-Reply-To: <d1c554290608171156h285d9b0ft79436f0f792e4214@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: a2e984ba-ead1-11e9-9d60-3106f5b1d025

> i don't know if that's too silly of me, but having this separation
> with this semantics (regular files vs service interfaces) doesn't goes
> against the idea that in plan9 one wouldn't have to differentiate
> between types of files unless he/she wishes so?

there are several different types of files, and
a few significant conventions,
so that /net is not interchangeable with /mnt, say.
put another way, things under /net deliberately present a
particular interface so that ndb/cs and dial will function,
regardless of what the names actually mean (ip vs datakit for instance).
if you try dialling things in /mnt, you're bound to be disappointed.

what plan 9 says is that to access anything, ultimately you
open a name, read/write, close.
it doesn't say that you don't differentiate between files,
and what you read and write will differ for /dev/draw as against
/net/tcp