From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Dennis' Draft of the Unix Timesharing System: not so draft?
Date: Mon, 19 Dec 2016 15:59:37 -0500 [thread overview]
Message-ID: <CAC20D2M93zPXUuh0zvQeK7KpPueKBs1j5fWjvKxD=eFZEehieg@mail.gmail.com> (raw)
In-Reply-To: <20161219201031.3259D18C0A1@mercury.lcs.mit.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2769 bytes --]
On Mon, Dec 19, 2016 at 3:10 PM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:
>
>
> 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? :-(
>
One of my favorite comparisons and definitions of "bloat" came when I
discovered years ago that the SVR3 >>boot<< system was larger than the V6
kernel.
>
>
> 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),
+1
> 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.
>
Mumble -- Other than one important idea (single-level-store as you said),
I'm not so sure. I think we ended up with most of what was envisioned,
and some of the SW things (like the "continuation" model and how
dyn-linking ended up working in practice) - I think we are ahead of
Multics. Winders more than UNIX (IMO) ended up with the complexity and
bloat and most of the bad ideas without the good. But I think UNIX mostly
was able to stick to what was important (except for the loss of "small is
beautiful" - my rant). Some of the HW idea moved on - Intel picked up
segments and rings. Look at INTEL*64, we use 2 rings and stopped using
using segments because it too hard to program around them --- both proved
to be unusable/impractical when they were released.
>
> (Of course, Multics made some mistakes - primarily 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.
I agree, and this may yet come back. It's too bad too many of the
younger engineers have not studied it. I was recently reviewing some stuff
from a couple of our younger Linux jockeys and they have re-invented
something like it. I smiled and said -- yes it >>is<< a great idea, but
it has been done.
> And wouldn't it be nice to have AIM boxes to run our browsers and
>
> mail-readers in - so much for malware!)
>
Indeed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20161219/0a844aac/attachment-0001.html>
next prev parent reply other threads:[~2016-12-19 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 20:10 Noel Chiappa
2016-12-19 20:50 ` Dan Cross
2016-12-19 20:59 ` Clem Cole [this message]
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='CAC20D2M93zPXUuh0zvQeK7KpPueKBs1j5fWjvKxD=eFZEehieg@mail.gmail.com' \
--to=clemc@ccc.com \
/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).