From: Al Kossow <aek@bitsavers.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Bitsavers' RT/PC, AIX, AOS, etc. recent additions
Date: Tue, 18 Feb 2020 05:39:59 -0800 [thread overview]
Message-ID: <6899aee0-6324-7b7e-513d-498a3cae6cd4@bitsavers.org> (raw)
In-Reply-To: <25E62EB5E090E7CB.c5cb28db-f209-4d75-8ad6-a165cb810b47@mail.outlook.com>
On 2/18/20 5:28 AM, Jason Stevens wrote:
> But I was really surprised about the coprocessor cards.. I wonder what other interesting things are in there. Or how hard it is to hammer
> 386 BSD into aos "sort of a 4.3 Tahoe ++"
I haven't dug into finding this yet, but wasn't there an RT netBSD?
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.
next prev parent reply other threads:[~2020-02-18 13:40 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 [this message]
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-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=6899aee0-6324-7b7e-513d-498a3cae6cd4@bitsavers.org \
--to=aek@bitsavers.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).