From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Dennis' Draft of the Unix Timesharing System: not so draft?
Date: Mon, 19 Dec 2016 15:10:31 -0500 (EST) [thread overview]
Message-ID: <20161219201031.3259D18C0A1@mercury.lcs.mit.edu> (raw)
> From: Warren Toomey
> Ritchie, D.M. The UNIX Time Sharing System. MM 71-1273-4.
> which makes me think that the draft version Doug McIlroy found
Not really a response to your question, but I'd looked at that
'UnixEditionZero' and was very taken with this line, early on:
"the most important features of UNIX are its simplicity [and] elegance"
and had been meaning for some time to send in a rant.
The variants of Unix done later by others sure fixed that, didn't they? :-(
On a related note, great as my respect is for Ken and Doug for their work on
early Unix (surely the system with the greatest bang/buck ratio ever), I have
to disagree with them about Multics. In particular, if one is going to have a
system as complex as modern Unices have become, one might as well get the
power of Multics for it. Alas, we have the worst of both worlds - the size,
_without_ the power.
(Of course, Multics made some mistakes - primarly in thinking that the future
of computing lay in large, powerful central machines, but other aspects of
the system - such as the single-level store - clearly were the right
direction. And wouldn't it be nice to have AIM boxes to run our browers and
mail-readers in - so much for malware!)
Noel
next reply other threads:[~2016-12-19 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 20:10 Noel Chiappa [this message]
2016-12-19 20:50 ` Dan Cross
2016-12-19 20:59 ` Clem Cole
2016-12-19 21:11 ` Dan Cross
2016-12-19 21:34 ` Clem Cole
2016-12-22 16:36 ` Tim Bradshaw
-- strict thread matches above, loose matches on Subject: below --
2016-12-17 22:34 Warren Toomey
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=20161219201031.3259D18C0A1@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.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).