From: Steve Kilbane <steve@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] micro vs monolithic kernels
Date: Tue, 10 Apr 2001 09:18:49 +0100 [thread overview]
Message-ID: <200104100818.JAA07235@localhost.localdomain> (raw)
In-Reply-To: Your message of "Mon, 09 Apr 2001 19:28:32 CDT." <Pine.LNX.3.96.1010409192732.14587v-100000@einstein.ssz.com>
> It's damn hard to 'use' a system if it isn't 'installed'.
True. But in general, a system is installed by a single individual over
a handful of hours, and then used by from one to thousands of individuals,
over periods that may last for years. Plan 9 isn't impossible to install,
and evidently many people have reached the end of the installation process,
and are using it. Therefore, evidently, it's worth paying attention to this
ratio.
From your other posts, it sounds like you're working on solving the
installation problems, though. Very nice, but it would have been nicer still
if you could have just said so, without attacking. The Bell folks are always
open and forthcoming about where their efforts fall short, be it because of
lack of resources, or lack of vision.
> Talk about specious distinctions.
About as specious as writing code that's coherent enough to be read by
someone else, or as putting coder/decoder complexities into the coder so
that the decoder just needs to stream. "Done once" versus "done lots" is
a pretty damn important difference.
When resources are limited, choices have to be made about where one
puts the effort. Indulge my curiosity, for a moment: if you'd being doing
it, Jim, which part of Plan 9 would you have dropped (i.e. not designed or
implemented) so that the time could be spent on the installation process?
steve
next prev parent reply other threads:[~2001-04-10 8:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 21:15 Russ Cox
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 [this message]
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=200104100818.JAA07235@localhost.localdomain \
--to=steve@whitecrow.demon.co.uk \
--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).