From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <82a974fdec1d7b1026e47ff473a8cd78@terzarima.net>
From: Charles Forsyth <forsyth@terzarima.net>
Date: Tue, 16 Dec 2008 20:21:45 +0000
To: 9fans@9fans.net
In-Reply-To: <20081216192511.GT9593@masters10.cs.jhu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Multiple '#s' ?
Topicbox-Message-UUID: 639bb85c-ead4-11e9-9d60-3106f5b1d025

>Or is there some active problem with the idea of multiple named
>pipe namespaces on one kernel?

they aren't named-pipe name spaces, but holders of arbitrary file descriptors,
which allows them to hold references to any open device, including network connections.
that means there's no problem in principle with having more than one.
one (incompatible) convention would be to make new ones and allow
an attach name such as #sxyz to refer to a particular instance, "xyz".
another variant, which is orthogonal, would allow directory structures
and track ownership.

named-pipe spaces are created by binding #| to a name, and each one is a new pipe.