From: David Arnold <davida@pobox.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Bitsavers' RT/PC, AIX, AOS, etc. recent additions
Date: Thu, 20 Feb 2020 12:44:28 +1100 [thread overview]
Message-ID: <CC50123A-58CC-44A1-8881-53D8DDD9B810@pobox.com> (raw)
In-Reply-To: <6899aee0-6324-7b7e-513d-498a3cae6cd4@bitsavers.org>
> On 19 Feb 2020, at 00:39, Al Kossow <aek@bitsavers.org> wrote:
<…>
> I've been interested in Mach since messing with MacMach on a IIfx in the early 90's
> Has there been any collective effort trying to recover RIG/Mach code?
> It all seems very fragmented.
I went looking for some of this a few months ago, but it seemed like it wasn’t going to be a simple search. At one time I’d played with CMU Mach, Utah Mach, OSF Mach, and Apple’s MkLinux, but it all seemed to have drifted into broken links and missing FTP servers.
Sprite, Accent, Spring, Amoeba, VSTa … a lot of the OS projects I remember from that era seem to have disappeared. Only Plan9 seems to have really survived (not counting the Mach bits of Darwin).
d
next prev parent reply other threads:[~2020-02-20 1:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 13:28 Jason Stevens
2020-02-18 13:39 ` Al Kossow
2020-02-20 1:44 ` David Arnold [this message]
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-20 6:44 ` [TUHS] anedotes: RT/PC VRM, (early) AIX compilers, IBM (Research) software release/pricing [was " Charles H. Sauer
2020-02-20 8:27 ` Kevin Bowling
-- strict thread matches above, loose matches on Subject: below --
2020-02-18 4:41 [TUHS] " 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
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=CC50123A-58CC-44A1-8881-53D8DDD9B810@pobox.com \
--to=davida@pobox.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).