9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu, kma@geneseo.edu
Subject: Re: [9fans] Pointers for using Plan 9?
Date: Thu,  5 Oct 2000 22:46:48 -0400	[thread overview]
Message-ID: <20001006024652.A210D199D9@mail> (raw)

	1. Sample Plan 9 setup and guidelines for decisions (I'm still
           pouring over the Overview to Plan 9 networks)

http://plan9.bell-labs.com/sys/doc/start.pdf is a start.

	2. Sample programs that use Plan 9 features

I think the most fundamentally Plan 9 aspect for a distributed
systems course is the easy sharing of resources.  Play around
with import, or with /mnt/term in cpu connections.

A nice demonstration is remote debugging via "import othermachine /proc".
An even better demonstration when the two machines are
different architectures.

An anecdote about remote resource sharing.
I have a private network with a few machines on it,
including a Windows box and a Linux box.  The Linux
box does not talk to the outside world, but the Windows
box can.  I wanted to ssh into the Linux box, but was
without my laptop (and thus my ssh key) and didn't even
have ssh installed on the Windows box.

I did, however, have my ssh key on another Plan 9 server,
accessible via the internet.  Without any encryption
software on the Windows box, I had no way to securely
get the ssh key.  Instead, I started up drawterm (a program
that pretends to be a Plan 9 terminal calling a cpu server)
and connected to the server with the ssh key.  Then I
ran ssh on the remote cpu server but driving the Windows box's
TCP stack underneath:

	bind /mnt/term/net/tcp /net/tcp
	ssh 1.2.3.4

All was well, and the ssh key never left the remote server.

Russ




             reply	other threads:[~2000-10-06  2:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-06  2:46 Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-10-06 18:11 David Gordon Hogan
2000-10-06 18:12 ` Boyd Roberts
2000-10-06 15:34 David Gordon Hogan
2000-10-06 15:40 ` Boyd Roberts
2000-10-06 16:06 ` Lucio De Re
2000-10-06  8:12 Richard Miller
2000-10-05 23:58 anothy
2000-10-05 17:01 Kirk M. Anne
2000-10-05 17:35 ` andrey mirtchovski
2000-10-06 14:04 ` Ish Rattan
2000-10-09  8:08   ` Fco. J. Ballesteros

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=20001006024652.A210D199D9@mail \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    --cc=kma@geneseo.edu \
    /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).