From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <3e1162e61003060713s1c9cc2c4i1b5e8d7deb9d335e@mail.gmail.com>
References: <b3b4f6f31003051937g6d3821cam7f078870390c128a@mail.gmail.com>
	<3e1162e61003060713s1c9cc2c4i1b5e8d7deb9d335e@mail.gmail.com>
Date: Sat,  6 Mar 2010 18:34:14 +0000
Message-ID: <df49a7371003061034v78789a26r714fdc65839eccb5@mail.gmail.com>
From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] acme(4) and addr=dot
Topicbox-Message-UUID: e17d21b0-ead5-11e9-9d60-3106f5b1d025

On 6 March 2010 15:13, David Leimbach <leimy2k@gmail.com> wrote:
> I think you want to create some kind of redirected handle to the ctl file
> first, then start a new block in rc. =C2=A0I believe this is how network
> programming in rc can be accomplished in Inferno as well. =C2=A0Is this n=
ot
> allowed in p9p? =C2=A0I've honestly not used the 9p commands too often.

the nearest you can get to it in p9p is something like:

{
  echo -n 'addr=3Ddot'
  9p read acme/70/addr
} | 9p write acme/70/ctl

but there's no way of guaranteeing that the read
takes place after the write - well, as a hack you can
put a sleep in there, but that's not great...