From: Duke Normandin <dukeofperl@ml1.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan9 topology
Date: Thu, 13 Jan 2011 13:24:00 -0700 [thread overview]
Message-ID: <alpine.DEB.2.00.1101131315090.4272@fryrpg-zna> (raw)
In-Reply-To: <4D2F5B74.5070908@gmail.com>
On Thu, 13 Jan 2011, John Floren wrote:
[snip]
> If you only have one computer available and have to dual-boot, you can
> actually do pretty good with a simple, standalone terminal (this is what
> gets installed by default). You can then get an account at one or two of
> the public Plan 9 servers and connect from your terminal.
Do you mean the Plan 9 terminal that you mention below? Roughly, what
does this installation include?
> If you have a second computer available that you can devote to Plan 9 (a
> Pentium II with 128 MB of RAM will perform admirably), I recommend that
> you find the instructions on the wiki for setting up a standalone CPU
> server
> (http://www.plan9.bell-labs.com/wiki/plan9/Configuring_a_standalone_CPU_server/index.html)
> and follow them. You will end up with a Plan 9 cpu/auth/file server all
> on one box, to which you can then connect from a Plan 9 terminal, 9vx on
> Linux, or drawterm on Linux/OS X/Windows.
I see! Plan 9 is essential a "server" OS. That's it! That's all! It
can't be run as a client and server all on one box.
> Personally, I've run at least half a dozen Plan 9 servers over the
> years, always installing a full cpu/auth/file server, usually on any PC
> I can scrape together out of the parts bin or the loading dock. Then I
> just connect from my desktop using drawterm, or I use the Thinkpad with
> Plan 9 installed as a terminal.
Been there; done that! with FreeBSD. :)
> Good luck; Plan 9 is a very fun system.
Sounds like it might be. Thanks for the input!
--
Duke
next prev parent reply other threads:[~2011-01-13 20:24 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 18:38 Duke Normandin
2011-01-13 18:48 ` dukeofperl
2011-01-13 18:50 ` David Leimbach
2011-01-13 19:16 ` Skip Tavakkolian
2011-01-13 19:31 ` Duke Normandin
2011-01-13 19:37 ` Jacob Todd
2011-01-13 19:44 ` Skip Tavakkolian
2011-01-13 20:08 ` Duke Normandin
2011-01-13 21:01 ` Tassilo Philipp
2011-01-13 21:39 ` Brian L. Stuart
2011-01-13 22:49 ` Duke Normandin
2011-01-14 3:27 ` blstuart
2011-01-14 4:02 ` erik quanstrom
2011-01-14 4:18 ` Duke Normandin
2011-01-14 4:04 ` Duke Normandin
2011-01-14 0:00 ` Federico G. Benavento
2011-01-14 3:26 ` Duke Normandin
2011-01-13 19:46 ` Bakul Shah
2011-01-13 20:11 ` erik quanstrom
2011-01-13 19:40 ` Duke Normandin
2011-01-13 20:07 ` John Floren
2011-01-13 20:24 ` Duke Normandin [this message]
2011-01-13 20:40 ` John Floren
2011-01-13 21:37 ` Duke Normandin
2011-01-13 21:59 ` Brian L. Stuart
2011-01-13 22:32 ` Duke Normandin
2011-01-13 23:18 ` John Floren
2011-01-14 3:42 ` Duke Normandin
2011-01-14 4:03 ` John Floren
2011-01-14 4:05 ` erik quanstrom
2011-01-14 4:15 ` Duke Normandin
2011-01-14 4:22 ` John Floren
2011-01-14 4:31 ` Duke Normandin
2011-01-14 4:35 ` Jacob Todd
2011-01-14 17:51 ` Bakul Shah
2011-01-14 17:54 ` erik quanstrom
2011-01-14 18:14 ` Bakul Shah
2011-01-14 19:13 ` erik quanstrom
2011-01-14 19:24 ` Duke Normandin
2011-01-14 20:44 ` Bakul Shah
2011-01-14 18:15 ` Charles Forsyth
2011-01-14 18:14 ` Federico G. Benavento
2011-01-14 18:35 ` Duke Normandin
2011-01-14 14:58 erik quanstrom
2011-01-14 17:14 ` Duke Normandin
2011-01-14 17:40 ` erik quanstrom
2011-01-14 18:58 ` Duke Normandin
2011-01-14 19:09 ` erik quanstrom
2011-01-14 19:23 ` Charles Forsyth
2011-01-14 19:22 ` Duke Normandin
2011-01-15 0:16 ` Charles Forsyth
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=alpine.DEB.2.00.1101131315090.4272@fryrpg-zna \
--to=dukeofperl@ml1.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).