From: Pete Wright <pete@nomadlogic.org>
To: tuhs@minnie.tuhs.org
Subject: [TUHS] Apollo Domain/OS
Date: Tue, 21 Jan 2020 11:02:38 -0800 [thread overview]
Message-ID: <46acce0f-9ce2-958b-9c12-c6d9c7f737d9@nomadlogic.org> (raw)
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
next reply other threads:[~2020-01-21 19:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 19:02 Pete Wright [this message]
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
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=46acce0f-9ce2-958b-9c12-c6d9c7f737d9@nomadlogic.org \
--to=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).