From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <009E0199-D15B-4985-8527-F3C14C32F824@bitblocks.com> References: <2A42D5A6-C7C1-4E40-A9B0-4E8F6591E079@bitblocks.com> <009E0199-D15B-4985-8527-F3C14C32F824@bitblocks.com> From: Charles Forsyth Date: Thu, 23 Feb 2017 12:40:24 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=94eb2c06f334c9b1af054931ea9d Subject: Re: [9fans] Upspin - a respin of 9p? Topicbox-Message-UUID: b518cd78-ead9-11e9-9d60-3106f5b1d025 --94eb2c06f334c9b1af054931ea9d Content-Type: text/plain; charset=UTF-8 On 23 February 2017 at 09:34, Bakul Shah wrote: > What seems to be missing is the namespace splicing (no bind or mount). That's a function of the operating system (or not), even with 9P, so nothing here rules that out. There are some interesting possibilities. --94eb2c06f334c9b1af054931ea9d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 23 February 2017 at 09:34, Bakul Shah <bakul@bitblocks.com> wrote:
What seems to be missing is t= he namespace splicing (no bind or mount).

That's = a function of the operating system (or not), even with 9P, so nothing here = rules that out.
There are some interesting = possibilities.

--94eb2c06f334c9b1af054931ea9d--