From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Vanilla Plan 9 or one of the flavors?
Date: Mon, 30 Dec 2013 23:33:12 -0500 [thread overview]
Message-ID: <33e2329fe3abd2d9d6341fe723cf76e2@brasstown.quanstro.net> (raw)
In-Reply-To: <CAFSuKHKQp1xYXBQCSa_hhsk93mPVwSLPMcLB5MSg4jXce8PMUg@mail.gmail.com>
On Mon Dec 30 21:03:24 EST 2013, alexander3223098@gmail.com wrote:
> Hi,
> After a number of months of lurking on this list, I've finally gotten
> a computer set up to be a dedicated Plan 9 installation (as part of a
> grid, of course).
> At this point, I need to choose between vanilla Plan 9 or one of the
> flavors (9front or 9atom). I have read the "9front vs. 9atom" thread;
> prevailing wisdom seems to say to go with 9atom unless you need the
> hardware support of 9front - please correct me if this is wrong.
> That being said, the thread didn't talk about the vanilla Plan 9
> distribution from Bell Labs. The computer I'm installing it on is ~15
> years old, so I doubt it will have all that many hardware support
> issues. Basically, would you guys recommend I try the Bell Labs
> distribution of Plan 9, 9front, or 9atom as my first installation?
> I've also done a cursory search of the list archives without finding
> anything; if this has been covered before, please accept my apologies.
well let me know if i can answer any questions or fix anything. funny how we all get
pigeon holed. i thought i did 9atom to support more hardware. :-)
- erik
next prev parent reply other threads:[~2013-12-31 4:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 2:02 Alex Jordan
2013-12-31 2:07 ` Alex Jordan
2013-12-31 4:33 ` erik quanstrom [this message]
2014-01-05 23:54 ` Alex Jordan
2014-01-06 0:03 ` Patryk Laurent
2014-01-06 4:03 ` Steven Stallion
2014-01-06 4:36 ` Lyndon Nerenberg
2014-01-06 4:41 ` Steven Stallion
2014-01-06 4:53 ` Lyndon Nerenberg
2014-01-06 5:01 ` Steven Stallion
2014-01-06 5:09 ` Lyndon Nerenberg
2014-01-06 5:13 ` andrey mirtchovski
2014-01-06 5:16 ` Steven Stallion
2014-01-06 5:28 ` Patryk Laurent
2014-01-06 5:12 ` Bruce Ellis
2014-01-06 15:35 ` a
2014-01-06 16:40 ` Aram Hăvărneanu
2014-01-06 16:54 ` Anthony Sorace
2014-01-06 17:21 ` lucio
2014-01-06 17:09 ` tlaronde
2014-01-06 17:25 ` lucio
2014-01-06 20:13 ` Kurt H Maier
2014-01-06 4:42 ` balaji
2014-01-06 20:05 ` Kurt H Maier
2014-01-06 7:08 ` Alex Jordan
2014-01-06 7:39 ` cinap_lenrek
2014-01-06 7:49 ` Alex Jordan
2014-01-06 10:48 ` Paul Clark
2014-01-06 17:29 ` Dave Eckhardt
2014-01-06 12:20 ` Richard Miller
2014-01-06 13:29 ` erik quanstrom
2014-01-07 6:58 ` Alex Jordan
2014-01-07 8:32 ` Andrés Domínguez
2014-01-07 14:00 ` erik quanstrom
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=33e2329fe3abd2d9d6341fe723cf76e2@brasstown.quanstro.net \
--to=quanstro@quanstro.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).