From: Clem Cole <clemc@ccc.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Apollo Domain/OS
Date: Tue, 21 Jan 2020 19:20:57 -0500 [thread overview]
Message-ID: <CAC20D2OfnqHaub+LCCB9q_imdqR0VSkDPRV4zzKpSoCVg6eWZw@mail.gmail.com> (raw)
In-Reply-To: <20200121230025.GL15860@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
Ted point taken. As I was driving home tonight I thought about both DCE and
UUIDs. The later is clearly important and we do owe the guys in Chelmsford
a great thank you for that one. But the registry ... really now.
On Tue, Jan 21, 2020 at 6:00 PM Theodore Y. Ts'o <tytso@mit.edu> wrote:
> On Tue, Jan 21, 2020 at 05:36:57PM -0500, Clem Cole wrote:
> > > 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.
> >
> > 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.
>
> The OSF/DCE's RPC system came from Apollo, as does the predecessor for
> the UUID layout still in use today (RFC 4122). Paul Leach brought
> both to the OSF, and as the Kerberos V5 Tech Lead, I worked with Paul,
> and used an early Internet-Draft spec of the OSF UUID and implemented
> it in e2fsprogs for labelling ext2/3/4 superblocks, and from there the
> infection vector spread to the GNOME project. When Paul brought both
> of those technologies to Microsoft when he went there after OSF went
> belly up.
>
> - Ted
>
--
Sent from a handheld expect more typos than usual
[-- Attachment #2: Type: text/html, Size: 1834 bytes --]
next prev parent reply other threads:[~2020-01-22 0:21 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
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 [this message]
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=CAC20D2OfnqHaub+LCCB9q_imdqR0VSkDPRV4zzKpSoCVg6eWZw@mail.gmail.com \
--to=clemc@ccc.com \
--cc=tuhs@minnie.tuhs.org \
--cc=tytso@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).