9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] micro vs monolithic kernels
Date: Mon,  9 Apr 2001 17:15:26 -0400	[thread overview]
Message-ID: <20010409211530.A859E19A09@mail.cse.psu.edu> (raw)

 	one question does anyone find bell labs' documentation a poor disgrace to
	software engineering's design process.

if we knew what it was going to look like when
we finished, what would be the point of building it?

more seriously, we're all happy to help you get going,
but setting up a plan 9 file or cpu server is not like
setting up a toaster.  it's not just going to work.
you need to get used to the way the system works so you
can figure out what went wrong when things do go wrong.

you wouldn't expect to set up a full-blown windows nt
file server in a few hours and have it work.  you wouldn't
(or at least shouldn't) expect to sit down with the red hat
box and have a linux system completely ready to go in a
few hours.  because plan 9 is a research system while those
are commercial systems, you should expect even less in terms
of `works right out of the box'.

that's not to say that it actually is harder to install than
windows or linux.  i think installing a terminal is actually
much easier in plan 9 than in the various linux distributions
i've used.  there's no similar program to lead you through
installing a cpu server, and certainly not one to lead you
through installing a file server.

if you go at it with the right frame of mind, plan 9
is a lot of fun and quite pleasant to use.
it _will_ be frustrating at times (especially when
setting up a file server), but in general those
times are few and far between, and it's more
rewarding than frustrating.

russ


             reply	other threads:[~2001-04-09 21:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09 21:15 Russ Cox [this message]
2001-04-09 21:52 ` Jim Choate
2001-04-09 21:36   ` Lyndon Nerenberg
2001-04-09 22:08     ` Jim Choate
2001-04-09 22:34       ` Lyndon Nerenberg
2001-04-09 23:08         ` [9fans] " Jim Choate
2001-04-09 22:50           ` Lyndon Nerenberg
2001-04-10  0:45       ` [9fans] " Steve Kilbane
2001-04-10  0:28         ` Jim Choate
2001-04-10  8:18           ` Steve Kilbane
2001-04-10  8:57       ` Douglas A. Gwyn
2001-04-09 21:40   ` William Josephson
2001-04-09 22:10     ` Jim Choate
2001-04-09 22:16       ` William Josephson
2001-04-09 22:42   ` Dan Cross
2001-04-09 23:10     ` Jim Choate
2001-04-10  0:30       ` Dan Cross
2001-04-09 22:10 ` Mike Haertel
  -- strict thread matches above, loose matches on Subject: below --
2001-04-17  8:35 nemo
2001-04-10 11:56 forsyth
2001-04-10 11:50 forsyth
2001-04-10 11:35 Matt
2001-04-10 10:52 forsyth
     [not found] <200104092210.RAA06371@einstein.ssz.com>
2001-04-09 22:12 ` Jim Choate
2001-04-10  9:00   ` Boyd Roberts
2001-04-09 22:00 jmk
2001-04-09 22:30 ` Jim Choate
2001-04-09 21:47 presotto
2001-04-09 21:43 Russ Cox
2001-04-09 22:16 ` Jim Choate
2001-04-10  8:59   ` Douglas A. Gwyn
2001-04-10  9:00   ` Boyd Roberts
     [not found] <john@cs.york.ac.uk>
2001-04-09 14:33 ` John A. Murdie
2001-04-09 23:31   ` Steve Kilbane
2001-04-09 10:19 forsyth
2001-04-09  9:09 forsyth
2001-04-09  9:32 ` Dave Iafrate - CSCI/F1997
2001-04-09 16:14   ` Douglas A. Gwyn
2001-04-08 19:36 presotto
2001-04-08 17:55 Andrey A Mirtchovski

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=20010409211530.A859E19A09@mail.cse.psu.edu \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).