9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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 15:49:22 -0700	[thread overview]
Message-ID: <alpine.DEB.2.00.1101131534140.4272@fryrpg-zna> (raw)
In-Reply-To: <781832.74065.qm@web83911.mail.sp1.yahoo.com>

On Thu, 13 Jan 2011, Brian L. Stuart wrote:

> > I could run a headless box as a Plan9 auth/cpu, fs server.  Then,
> > if I want to this Plan9 server, is there a minimum Plan9 install
> > that I could put on the spare partition that I have?
>
> With this setup available, there are several ways you can go.  As a
> lot of people have suggested, you can install a cpu/auth/fs server
> on the headless machine and use drawterm to be a terminal talking to

Got it!

> him.  An even more Plan9-like way of doing it is to net-boot a Plan9
> terminal from your cpu/auth/fs machine.  If you want to boot your
> main box that way, you can without installing anything on it.  From
> within Linux, you can do the same thing in virtualbox.  In fact, I
> have a virtualbox terminal running right now on my machine.  It's
> net booted, taking its Plan9 kernel from a Plan9 machine that
> provides DHCP service and it mounts its root from a Ken FS machine.
> At home, I use 9vx taking its root from a Plan9 fossil/venti file
> server.

So the NIC in your Linux box must have to be PXE capable? Truth be
told, I've never set up a net-booting system. The Plan ( server would
have to have enough disk space to store its own stuff, plus the
workstation's file system? Could get dicey, if you've got a few
workstations net-booting, could it not?

> > for a long time: a 486DX running FreeBSD as a mailserver; another
> > running as a webserver; another couple running primary and slave
> > nameservers; and one dual-homed FreeBSD box routing and doing
> > firewall/natd.
>
> The only problem you'd run into there is that Plan9 doesn't
> currently have a NAT implementation.

I should be able to hang the Plan 9 server off my router without any
problems, should I not? The router NATs ..

> > The above sounds like a job for Plan9 :) But my point is - is that
> > I don't need to set up a LAN to enjoy Linux or FreeBSD. Can I use
> > Plan9 standalone in a dedicated partition?
>
> Yes, the default install from the CD sets up a stand-alone machine.
> And for most of us, that's the starting point from which we
> configure any specialized machines such as cpu, auth, or file
> servers.  And you can get a pretty good feel for what Plan9 is about
> with a stand-alone machine.  However, some parts of the system make
> a lot more sense when you experience them in a networked
> environment.  Auth is a good example of this.

I see your point - because Plan 9 was after all, built as a
distributed system. I'll give it a shot on that P-I mentioned in
another post.

> But whichever path(s) you take, I hope you'll find Plan9 is a great
> system, just as we do.

I'm in trouble already ...
--
Duke



  reply	other threads:[~2011-01-13 22:49 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 [this message]
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
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.1101131534140.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).