The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Chris Hanson <cmhanson@eschatologist.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Apollo Domain/OS
Date: Tue, 21 Jan 2020 17:36:57 -0500	[thread overview]
Message-ID: <CAC20D2MBb=UavxQkePdvC20W7WJUEaw9xcuGQGh-c=2rkAxP_Q@mail.gmail.com> (raw)
In-Reply-To: <DEE23024-04E3-4A37-AD17-41EC725B8B0A@eschatologist.net>

[-- Attachment #1: Type: text/plain, Size: 2566 bytes --]

On Tue, Jan 21, 2020 at 5:03 PM Chris Hanson <cmhanson@eschatologist.net>
wrote:

> My understanding is that there’s a direct line from MULTICS to Prime to
> Apollo,

Yes in some ways...



> in that Apollo was founded by former Prime folks who took their philosophy
> with them.
>
Actually not quite.  MIT/Multics to Honeywell to Pr1me to Apollo (to
Belmont/Stellar)  Bill P and his former TA from MIT (Mike Spourer) actually
wanted to break a little when they did Apollo.  The whole ideas was too
risky for Honeywell, so he created Pr1me.    Apollo was too risky for Pr1me
so he created Apollo.  Stellar was too risky for Apollo so he created
Belmont - a.k.a. Stellar.

[By the way, I spoke to Bill over the holidays.  He's a still the same].

>
> Apollo’s operating system (Aegis, Domain, Domain/OS) had a lot of good and
> interesting ideas and was quite influential

I absolutely agree.

But a number new idea were from an influx of MIT and ex-DEC folks
actually.  And that that terrible sin called the registry that lives on
winders came from Paul (some of us thought it was a bad idea then too BTW).

IMO: The best idea was the typed file system and the ability to run user
code specific with a file type.  That's how IP, TCP, UDP are all
implemented.  Very, very cool.  There is a USENIX paper that describes it
I'll have to dig up the reference.  It's worth reading.  But I have never
seen it implemented again as well.




> A lot of what we take for granted today in distributed computing came via
> Apollo more than anywhere else, as Apollo users and alumni took what they
> learned to other systems.
>
Yes and no.   I agree it was a wonderful intellectual playground for some
very cool ideas.   Some worked pretty well, but not all did.  For example,
as Larry said earlier today, the "twin'ed" or diskless nodes were awful
(replace the S with C for what many of us think about them).  But it got
Sun to make them too and ended up being a great add-in disk business
later.  I refused at Masscomo and ended up losing war, even though the cost
of a WS500 was less than a Sun2 with a disk, people bought Sun's diskless
and then after they discovered they sucked, spent another 6K to buy a desk
system for them (we lost for economics, but I was technically right -
a.k.a. Cole's law of economics vs. sophisticated technology).

Anyway, we (as a community) are better for having that system but other
than the registry, I can think of little actual technology that we continue
to use from Aegis.

[-- Attachment #2: Type: text/html, Size: 4495 bytes --]

  reply	other threads:[~2020-01-21 22:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 19:02 Pete Wright
2020-01-21 19:14 ` Larry McVoy
2020-01-21 21:28 ` Dan Cross
2020-01-21 21:52   ` Chris Hanson
2020-01-21 22:36     ` Clem Cole [this message]
2020-01-21 22:43       ` Kevin Bowling
2020-01-21 22:58       ` Charles H Sauer
2020-01-21 23:00       ` Theodore Y. Ts'o
2020-01-22  0:20         ` Clem Cole
2020-01-22  1:18         ` Richard Salz
2020-01-22 16:31           ` Paul Winalski
2020-01-22 18:06             ` Pete Wright
2020-01-22  0:25     ` Jon Steinhart
2020-01-22  7:11     ` Lars Brinkhoff
2020-01-21 22:09   ` Dennis Boone
2020-01-21 23:53   ` Ronald Natalie
2020-01-22  2:47     ` Chris Hanson

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='CAC20D2MBb=UavxQkePdvC20W7WJUEaw9xcuGQGh-c=2rkAxP_Q@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=cmhanson@eschatologist.net \
    --cc=tuhs@minnie.tuhs.org \
    /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).