From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon, 17 Nov 2008 07:57:02 +0000
From: Eris Discordia <eris.discordia@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-ID: <6930BFF8599B170702405D8C@[192.168.1.2]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [9fans] Do we have a catalog of 9P servers?
Topicbox-Message-UUID: 46bf08ba-ead4-11e9-9d60-3106f5b1d025

This explanation isn't immediately comprehensible to me--I guess I'll have
to read the man pages and some other documentation and then come back to
understand this.

Thanks anyway.

--On Sunday, November 16, 2008 4:52 PM -0500 erik quanstrom
<quanstro@quanstro.net> wrote:

>> the same time. I thought Plan 9's approach eliminated that by keeping a
>> distinct instance of the stack for each imported /net.
>
> not quite.
>
> referencing '#In' for the first time will cause the nth
> ip stack to be created.  subsequent references do not create
> a copy.
>
> it's also important to note that import doesn't operate on
> devices directly (except in the degnerate case of
> '#D' for some device D).  import builds a new namespace
> according to the recipie in /lib/namespace (cf. namepace(6))
> on the importee. so /net references that namespace, not a device.
> obviously '#t' still references a device on the importee.
>
> - erik
>
>