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 21:04:18 -0700 [thread overview]
Message-ID: <alpine.DEB.2.00.1101132045420.4272@fryrpg-zna> (raw)
In-Reply-To: <f6202a7cb6b4bd1f896fc6160f948a95@bellsouth.net>
On Thu, 13 Jan 2011, blstuart@bellsouth.net wrote:
[snip]
> > So the NIC in your Linux box must have to be PXE capable?
>
> It depends. If you want to PXE boot the box directly and have
> it run the Plan9 kernel natively, then at some point, something
> will have to be PXE capable. That could be the machine's BIOS
> or BIOS code on the NIC or even a boot loader loaded from a
> disk or CD or...
Got it ...
> On the other hand, for the case of virtualbox the PXE booting
> support is built into virtualbox itself.
ummm...
> > Truth be
> > told, I've never set up a net-booting system.
>
> Because Plan9 was designed from the ground up around a network
> organization, it does a good job of supporting net booting. It's
> not hard to set up.
>
> > 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?
>
> It can. The clients all share a single copy of the common files,
> but each user will have his own files on the common server.
> But the full Plan9 installation is quite managable. You can
> do quite a lot with only a few gig.
Yeah! It's only going to be me using the server. So it's not like I'm
going to hit it that hard. Can I run several Plan9 boxen, each
dedicated to a task - like mail; named; httpd, etc. All headless, but
just purring away ;)
[snip]
> > I'm in trouble already ...
>
> Rotfl... You will be assimilated :) Seriously though, the Plan9
> community is a good bunch and everyone is happy to help anyone
> who genuinely wants to learn.
I sense that already. I've got _a lot_ to learn; but I'm willing. BTW,
I'm just a 63yr old programmer / networking hobbyist - all
self-taught. As I said in another post, my networking experience
started when I discovered FreeBSD - some 15 years ago. I've had some
nice LANs running - all before WIFI, and before routing appliances
were available. No probs. I enjoy it. Starting over with Plan9 is
going to be fun.
> My suggestion would be to work on your spare machine first.
> You won't have to worry about blowing anything away and
> it might evolve into a useful part of your network. I'd also
> start by installing from the CD as a stand-alone machine.
> After you know your way around some, you can try to convert
> it to a combined CPU/auth/file server and then look into
> how you connect to it from other machines.
Sounds like a plan -- pun intended! Much obliged!
--
Duke
next prev parent reply other threads:[~2011-01-14 4:04 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 [this message]
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.1101132045420.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).