9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] looking for advice for network setup
Date: Thu, 11 Aug 2011 17:39:50 -0400	[thread overview]
Message-ID: <C1CB3C7C-E671-4130-9AA2-15495E9A299D@9srv.net> (raw)
In-Reply-To: <CAEFe=zpAuyz39DD7bqZ8AL4uCebep1TqC5a15LZCkv+4RaPy_g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]

i'm not 100% clear on what you're after, but when i had a similar setup, i
wanted to be able to get at my home (NATed) data from work. to do so, i
have a script called postroot [1] which, when cpu'd into a server posts the
root of the calling terminal as foo.root, where foo is the calling terminal. i
could then "mount /srv/foo.root /n/foo" or similar to get at my home box.

it was occasionally useful to be able to use the home network connection
from outside, too. for that, i have a script called tun[2] which mounts the
network connection from a named root (previously posted with postroot)
and connects using that.

there's no special server needed; this is all using the standard tools. i'm
not clear what you mean about giving terminals an updated namespace.

you could stick an entry in cron on the NATed system that calls postroot
on the real-world server. in that case postroot ought to do a bit more
error checking and probably try the existing connection before removing
and replacing it.

the structure, and possibly the actual scripts (i don't remember) came
from someone in #plan9, possibly maht.

[1]	/n/sources/contrib/anothy/bin/rc/postroot
[2]	/n/sources/contrib/anothy/bin/rc/tun


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 210 bytes --]

  reply	other threads:[~2011-08-11 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 20:38 Roman Salmin
2011-08-11 21:39 ` Anthony Sorace [this message]
2011-08-12 13:50   ` Roman Salmin
2011-08-12 15:55     ` Anthony Sorace
2011-08-12 18:27       ` Steve Simon

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=C1CB3C7C-E671-4130-9AA2-15495E9A299D@9srv.net \
    --to=a@9srv.net \
    --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).