From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <7cbf5a4fb2e96d0fe675c8903d0dcc83@ipgp.jussieu.fr> References: <138575260904210339wcdac3e6o8f9af4b3e4811447@mail.gmail.com> <7cbf5a4fb2e96d0fe675c8903d0dcc83@ipgp.jussieu.fr> Date: Tue, 21 Apr 2009 11:18:19 -0400 Message-ID: <509071940904210818h3b470282v13722ac6ae926c22@mail.gmail.com> From: Anthony Sorace To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] exporting a namespace Topicbox-Message-UUID: ed4cedc8-ead4-11e9-9d60-3106f5b1d025 On Tue, Apr 21, 2009 at 07:17, Mathieu Lonjaret wrote: // Running 9vx is not exactly the same as running a cpu/file server... This is certainly true, but isn't really relevant here. If you're looking to do ad hoc sharing, the easiest way is probably with listen1, exportfs, and import. I just tested this in two 9vx instances on the same machine (which already had my normal one running): 9vx 1: :; 9fs wiki post... :; ls /mnt/wiki | wc 235 235 6413 :; aux/listen1 -tv 'tcp!*!12345' /bin/exportfs (the -v isn't really needed there) 9vx 2: :; ls /mnt/wiki :; import -A tcp!localhost!12345 /mnt/wiki :; ls /mnt/wiki | wc 235 235 6413 aux/listen1 grabs a network port (tcp port 12345 on all interfaces, in this invocation) and when a new connection comes in, runs /bin/exportfs, which has a little protocol to negotiate what namespace to export and then exports it. on the other host, import dials the exportfs listener started above and mounts the /mnt/wiki exported there on its own namespace. that's my understanding of what you're after, anyway. if there's something else you're looking for, just drop a note.