From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <d62e1b7fa9afbb3f79f2552ec96a4bbd@brasstown.quanstro.net>
References: <20101105102946.GA12171@shutemov.name>
	<AANLkTi=mb5T+Fhu+aaKvrDc+o2x7vCN65TnN+ATDdOF=@mail.gmail.com>
	<8f55d962591f55cf217f8070f78dfa3b@coraid.com>
	<AANLkTi=KTpWad2QCwp1fH2uyEq3NDVG3O2mLmMp2-592@mail.gmail.com>
	<d62e1b7fa9afbb3f79f2552ec96a4bbd@brasstown.quanstro.net>
Date: Fri,  5 Nov 2010 14:40:27 -0700
Message-ID: <AANLkTikzcC=E7Tts8hFd3xzpHqYF9S7qZn-se5PGcEF0@mail.gmail.com>
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [9fans] Passing a file descriptor between processes
Topicbox-Message-UUID: 787ccc1e-ead6-11e9-9d60-3106f5b1d025

i wish #s had a directory structure and enforced group permissions.

On Fri, Nov 5, 2010 at 5:21 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>> Currently, if your processes have a common parent, you can use rfork; if
>> not, you must resort to #s. '#s' is a pretty unfortunate interface,
>> though...
>
> okay, practicially speaking, what's wrong with #s, and what do you propose?
>
> - erik
>
>