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:08:29 -0700 [thread overview]
Message-ID: <alpine.DEB.2.00.1101131247560.4272@fryrpg-zna> (raw)
In-Reply-To: <AANLkTim+sHhDyWvS08zqx-FJu--RBgDuCYbO5E5MSWvP@mail.gmail.com>
On Thu, 13 Jan 2011, Skip Tavakkolian wrote:
> On Thu, Jan 13, 2011 at 11:31 AM, Duke Normandin <dukeofperl@ml1.net> wrote:
> > On Thu, 13 Jan 2011, Skip Tavakkolian wrote:
> >
> >> if the intent is to get a full understanding of what an operational
> >> Plan 9 environment is like, using VMware or Qemu to create VM's for
> >> various roles (auth/cpu, fs, term) connected by a virtual network is
> >> an excellent option. I've successfully used this setup for
> >> experimenting/testing and for demos.
> >
> > Sounds like _a lot_ of fooling around! I've set up numerous *nix LANs
> > before, but don't have one at the moment. How much memory would a
> > machine need to set up all those VMs?
> depending on the host os, 1g is sufficient. i've never needed to use
> more than 256M for plan9 vm's.
The box that I'd be using has a total of 1G RAM. If I do this, it
would be on top of Xubuntu 10.10. But the VM thing doesn't really
appeal to me.
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? Kinda like what I had
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. Had a couple of Linux and FreeBSD workstations hung on
this LAN. Those 486DX _never_ hiccuped! (Thank you UPS!!!)
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?
--
Duke
next prev parent reply other threads:[~2011-01-13 20:08 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 [this message]
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
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.1101131247560.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).