From: Kevin Bowling <kevin.bowling@kev009.com>
To: Jason Stevens <jsteve@superglobalmegacorp.com>
Cc: TUHS <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Bitsavers' RT/PC, AIX, AOS, etc. recent additions
Date: Mon, 17 Feb 2020 21:53:54 -0700 [thread overview]
Message-ID: <CAK7dMtBqctAj7ndVGqi9Q2Zz-mbr1Ce7QCRcVN2grQLxwXMm7A@mail.gmail.com> (raw)
In-Reply-To: <25E62EB5E090E7CB.88de76ea-9cec-4c1e-a00f-b15eb755ab0a@mail.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
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
Regards,
Kevin
On Mon, Feb 17, 2020 at 9:43 PM Jason Stevens <
jsteve@superglobalmegacorp.com> wrote:
> Interesting stuff! And another version of Mach is buried in there.
>
> So the 4 csrg cd set may have updates to the romp support as it's an older
> version of the 5.1 kernel from 89... Not that think there is any Mach romp
> users.
>
> Get Outlook for Android <https://aka.ms/ghei36>
>
> ------------------------------
> *From:* TUHS <tuhs-bounces@minnie.tuhs.org> on behalf of Charles H Sauer <
> sauer@technologists.com>
> *Sent:* Tuesday, February 18, 2020, 5:51 a.m.
> *To:* TUHS
> *Subject:* [TUHS] Bitsavers' RT/PC, AIX, AOS, etc. recent additions
>
> The Bitsavers' RSS feed (
> http://user.xmission.com/~legalize/vintage/bitsavers-bits.xml) seemed to
> me to be dominated by RT, AIX, AOS (BSD for RT), etc. stuff in the last
> week or so. I've only sampled a few items, but discovered a few things that
> I should have known (or knew and forgot?) while I was at IBM.
> http://www.bitsavers.org/pdf/ibm/pc/rt/ -- voice: +1.512.784.7526 e-mail:
> sauer@technologists.com fax: +1.512.346.5240 Web: https://technologists.com/sauer/
> Facebook/Google/Skype/Twitter
> <https://technologists.com/sauer/Facebook/Google/Skype/Twitter>:
> CharlesHSauer
>
[-- Attachment #2: Type: text/html, Size: 2873 bytes --]
next prev parent reply other threads:[~2020-02-18 4:54 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 [this message]
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
-- 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=CAK7dMtBqctAj7ndVGqi9Q2Zz-mbr1Ce7QCRcVN2grQLxwXMm7A@mail.gmail.com \
--to=kevin.bowling@kev009.com \
--cc=jsteve@superglobalmegacorp.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).