The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kevin Bowling <kevin.bowling@kev009.com>
To: Chris Hanson <cmhanson@eschatologist.net>
Cc: TUHS <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Bitsavers' RT/PC, AIX, AOS, etc. recent additions
Date: Wed, 19 Feb 2020 18:24:01 -0700	[thread overview]
Message-ID: <CAK7dMtC99uO=EThLup2yqwB6b-Rs7Op5d-tytxkmi-y4dnmxug@mail.gmail.com> (raw)
In-Reply-To: <226AD6CE-1B73-43FA-9156-114AAAB4EB80@eschatologist.net>

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

Neat!  Do you think we will ever be able to recover those bits or is it too
obscure and unobtanium like the rs6000 Mach port?

As an aside I’ve near complete technical references for both of these
platforms (RT, rs6000) and they were quite comprehensive for doing OS
ports. I wondered why there was no free open source OS for them but I now
suspect people just had fear of IBM, some real and some imagined.

On Wed, Feb 19, 2020 at 6:17 PM Chris Hanson <cmhanson@eschatologist.net>
wrote:

> On Feb 17, 2020, at 8:53 PM, Kevin Bowling <kevin.bowling@kev009.com>
> wrote:
> >
> > Can you clarify what is Mach in this archive if I have a gap in my
> knowledge? I didn’t know the VRM had any direct relationship to Mach
>
> It didn’t, but CMU used Mach on the RT, including in public clusters[1].
>
> CMU also deployed MacMach on the Macintosh II in public clusters, which
> ran System 6 side-by-side with BSD 4.3.
>
>   -- Chris
>
> [1] A “public [computer] cluster” was CMU terminology for computer labs
> accessible to the entire CMU community instead of just being accessible to
> one department or program.
>
>
>

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

  reply	other threads:[~2020-02-20  1:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18  4:41 Jason Stevens
2020-02-18  4:53 ` Kevin Bowling
2020-02-18  8:01   ` Jason Stevens
2020-02-18  8:04     ` Kevin Bowling
2020-02-18 12:29       ` Jason Stevens
2020-02-18 13:01         ` Kevin Bowling
2020-02-18 11:31     ` Al Kossow
2020-02-20  1:17   ` Chris Hanson
2020-02-20  1:24     ` Kevin Bowling [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-18 13:28 Jason Stevens
2020-02-18 13:39 ` Al Kossow
2020-02-20  1:44   ` David Arnold
2020-02-20  2:03     ` Al Kossow
2020-02-20  2:09       ` Bakul Shah
2020-02-20  7:18     ` arnold
2020-02-18 13:41 ` Kevin Bowling
2020-02-17 21:50 Charles H Sauer
2020-02-18  1:30 ` Al Kossow
2020-02-20  1:29   ` 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='CAK7dMtC99uO=EThLup2yqwB6b-Rs7Op5d-tytxkmi-y4dnmxug@mail.gmail.com' \
    --to=kevin.bowling@kev009.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).