From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <31c6143cade0915c81da9191429d9807@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed, 22 Aug 2007 07:30:03 -0400
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: everything is a directory
In-Reply-To: <1187776240.695036.278770@x40g2000prg.googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: afe1ddf6-ead2-11e9-9d60-3106f5b1d025

> In OO you are _always_ composing stuff from at least two sets of data
> and functions: the data and functions of parent, and the data and
> functions of the new child you are creating. In Plan 9, the standard /
> net might represent the parent, and /my/net that you bind on top of it
> represents the new data and new functions you create, in purpose of
> modifying the parent.

i think you're missing some important bits, and i think you misunderstand
the culture.  you might want to read ip(3) for information on how /net
is really structured.  even supposing that each process had it's own network
stack (which they do not), it's doubtful that /my/net would be the choice.
namespace(6) describes how /lib/namespace is interpreted to build an
initial namespace.

- erik