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

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.



  parent reply	other threads:[~2020-02-20  1:18 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 [this message]
2020-02-20  1:24     ` Kevin Bowling
  -- 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=226AD6CE-1B73-43FA-9156-114AAAB4EB80@eschatologist.net \
    --to=cmhanson@eschatologist.net \
    --cc=kevin.bowling@kev009.com \
    --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).