[9fans] /net like file trees and scripting.

["Roman V. Shaposhnick" <vugluskr@unicorn.math.spbu.ru>]

While doing C programming and using /net/tcp for example in its
raw form ( without dial & co. ) I had no problems whatsoever since
everything was confined in one process.

The problem showed up when I tried to do roughly the same in rc. E.g.:

$ cat t
#!/bin/rc

a=`{cat /net/tcp/clone}
echo -n 'connect lambda!7' > /net/tcp/$a/ctl
cat /net/tcp/$a/status
echo 'hello' > /net/tcp/$a/data
cat /net/tcp/$a/data

$ ./t
Time_wait srtt 0 mdev 0 cwin 1461 swin 24820 rwin 65535 timer.start 200 timer.count 190 rerecv 0
echo: write error: i/o on hungup channel

As far as I can tell, I can't get away with this since /net/tcp/clone is being
closed before /net/tcp/$a/data gets opened and there is no way for me to
change that since first cat and subsequent cats are different process. And
of course they close everything on exit.

Am I doomed to use C in such case, or is there any clever way to trick the
system ?

Thanks,
Roman.