From: Dan Cross <crossd@gmail.com>
To: Pete Wright <pete@nomadlogic.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Apollo Domain/OS
Date: Tue, 21 Jan 2020 16:28:16 -0500 [thread overview]
Message-ID: <CAEoi9W4o-qPs9JskMCmca+c9M3pqcmL3kPcANQ4Jb=cwJkVkSg@mail.gmail.com> (raw)
In-Reply-To: <46acce0f-9ce2-958b-9c12-c6d9c7f737d9@nomadlogic.org>
[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]
To my knowledge, there was never a link between Plan 9 and Domain/OS.
As I understood it, Domain/OS was more influenced by Multics and maybe the
Pr1me machines than anything else. Plan 9 came from the Unix heritage (and
thus had Multics as a grandparent, in a manner of speaking).
If there was any connection at all, I suspect it was tenuous and more in
the form of an indirect influence, such as an idea someone got from a paper
or something like that.
- Dan C.
On Tue, Jan 21, 2020 at 2:11 PM Pete Wright <pete@nomadlogic.org> wrote:
> Apologies that this isn't specifically a Unix specific question but I
> was wondering if anyone had insight in running domain/OS and it's
> relationship to Plan 9 (assuming there is any).
>
> One of my early mentors was a former product person at Apollo in Mass.
> and was nice enough to tell me all sorts of war stories working there.
> I had known about Plan9 at the time, and from what he described to me
> about domain/OS it sounded like there was lots of overlap between the
> two from a high level design perspective at the least. I've always been
> keen to understand if domain/OS grew out of former Bell Labs folks, or
> how it got started.
>
> As an aside, he gifted me a whole bunch of marketing collateral from
> Apollo (from before the HQ acquisition) that i'd be happy to share if
> there is any historical value in that. At the time I was a
> video/special effects engineer are was amazed at how beneficial having
> something like domain/OS or Plan9 would have been for us, it felt we
> were basically trying to accomplish a lot of the same goals by duct
> taping a bunch of Irix and Linux systems together.
>
> Cheers,
> -pete
>
> --
> Pete Wright
> pete@nomadlogic.org
> @nomadlogicLA
>
>
[-- Attachment #2: Type: text/html, Size: 2308 bytes --]
next prev parent reply other threads:[~2020-01-21 21:29 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 [this message]
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
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='CAEoi9W4o-qPs9JskMCmca+c9M3pqcmL3kPcANQ4Jb=cwJkVkSg@mail.gmail.com' \
--to=crossd@gmail.com \
--cc=pete@nomadlogic.org \
--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).