9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] So, why Plan 9?
Date: Tue, 12 Oct 2010 15:53:09 +0100	[thread overview]
Message-ID: <1467c594bbd185def5747e912e2b3fd5@quintile.net> (raw)
In-Reply-To: <a4470c09-4800-4ec5-9763-9fda0010b1b0@f25g2000yqc.googlegroups.com>

the twitter example you gave is perhaps too simple, could the tweets
not just be text written to a publicly writable file. the users could connect
with 9p but as the user none son they will need no auth.

better examples of the everything is a file aproach are wikifs (a file server which
prvides virtual files for the httpd server (or any normal 9p file client)
to access and stores a database of wiki pages.
http://plan9.bell-labs.com/magic/man2html/4/wikifs

the cassic example is using a plan9 server as a gateway machine across a firewall.
This machine is dual homed and all machines inside the firewall are isolated.
when one of these machines wants to connect to somone outside the firewall they
can just import the gateway's /net.alt over the top of their own. (by tradition
the primary interface is mounted on /net and the seccondary at /net.alt)

Now any DNS lookup and  socket connection will be made using the gateway's internet
facing NIC. This is all done using the 9p protocol, no clever IP routing etc.
if the 9p connection to the hateway happens to come over an ssh session,
ppp, or pigeon, it doesn't matter, you are sharing files, and these particular
files give you access to that machines network interface.

there is also a really neat trick you can use do a similar thing with a unix
machine as the gateway - sshnet provides a /net like interface to plan9 but uses
ssh's remote port forwarding to speak to unix:
http://plan9.bell-labs.com/magic/man2html/1/ssh

-Steve



  reply	other threads:[~2010-10-12 14:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11  9:05 Mark Carter
2010-10-11 10:23 ` Sergey Zhilkin
2010-10-11 11:07 ` Robert Raschke
2010-10-11 11:17   ` Robert Raschke
2010-10-11 11:53     ` Nick LaForge
2010-10-11 13:39       ` Bruce Ellis
2010-10-11 14:45         ` ron minnich
2010-10-11 15:01         ` Karljurgen Feuerherm
2010-10-12  8:33       ` Aleksandar Kuktin
2010-10-12  8:51         ` Max E
2010-10-12 14:47           ` David Leimbach
2010-10-12 11:25         ` Steve Simon
2010-10-12 12:24         ` Jacob Todd
2010-10-12 16:04         ` Aleksandar Kuktin
2010-10-11 18:43     ` Brian L. Stuart
2010-10-12  8:17       ` Anssi Porttikivi
2010-10-12 14:09         ` Mark Carter
2010-10-12 14:53           ` Steve Simon [this message]
2010-10-12 14:59             ` David Leimbach
2010-10-12  9:06 ` Max E
2010-10-12  9:29   ` yy

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=1467c594bbd185def5747e912e2b3fd5@quintile.net \
    --to=steve@quintile.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).