From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <df49a7370711090454q40cfadecqd1e515695ea134e9@mail.gmail.com>
Date: Fri,  9 Nov 2007 12:54:32 +0000
From: "roger peppe" <rogpeppe@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] query on styxlisten (Inferno) and mount (Linux)?
In-Reply-To: <8C876307-637F-443A-BB74-F54D3A7E6157@utopian.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <8C876307-637F-443A-BB74-F54D3A7E6157@utopian.net>
Topicbox-Message-UUID: f037f494-ead2-11e9-9d60-3106f5b1d025

> This exports the entire Inferno root. Styxlisten will start a
> listener and return, so I don't think you need the "&". 564 is the
> usual 9p port.

it might be worth noting that when the command run by
styxlisten exits, styxlisten kills the listener, assuming the
command is no longer around to take calls.

FWIW, for a simple export, i usually do the equivalent:

     listen addr {export /&}

in this case the & is necessary, as listen doesn't listen
for any more calls while the command is running.
this is actually useful behaviour - when i want to mount
the namespace of a machine i can't run a listener on
(e.g. because some firewall blocks incoming calls)
i can do:

    listen -s addr {mount -A /fd/0 /n/remote; raise break}

and on the exporting machine:

    dial addr {export /&}

it's quite flexible.