9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] exporting a namespace
Date: Tue, 21 Apr 2009 17:40:36 +0200	[thread overview]
Message-ID: <138575260904210840u6312f388u51508955e6fa3d04@mail.gmail.com> (raw)
In-Reply-To: <509071940904210818h3b470282v13722ac6ae926c22@mail.gmail.com>

This was exactly what I was trying to do, thank you very much.
It works just fine in 9vx.
Saludos

2009/4/21, Anthony Sorace <anothy@gmail.com>:
> 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.
>
>


--
Hugo



  reply	other threads:[~2009-04-21 15:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 10:39 hugo rivera
2009-04-21 11:17 ` Mathieu Lonjaret
2009-04-21 11:26   ` hugo rivera
2009-04-21 15:18   ` Anthony Sorace
2009-04-21 15:40     ` hugo rivera [this message]
2009-04-21 15:54       ` ron minnich
2009-04-21 16:03         ` hugo rivera
2011-01-15 20:14           ` ron minnich
2011-01-16 15:43             ` hiro
2011-01-16 20:04               ` ron minnich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=138575260904210840u6312f388u51508955e6fa3d04@mail.gmail.com \
    --to=uair00@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).