From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Charles H Sauer <sauer@technologists.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] one element of one of M factions of N companies [Re: Amdahl UTS, AIX/370, AIX/ESA
Date: Tue, 5 Nov 2019 19:06:00 -0500 [thread overview]
Message-ID: <20191106000600.GD26959@mit.edu> (raw)
In-Reply-To: <86352c85-1b06-6035-de4a-5b5a64f1cf98@technologists.com>
On Tue, Nov 05, 2019 at 04:11:11PM -0600, Charles H Sauer wrote:
> It has been illuminating, surprising, but not shocking, the last week of so,
> to learn from from posts here, that AIX/370 was hard to get and mostly a
> university offering. What we (AIX people associated with RT/PC and then
> RS/6000) were told was that "everybody", especially Federal customers,
> wanted what became known as TCF (the original Locus work) for 370 and PS/2.
> I remember one Federal Systems Division person who seemed especially
> effective as a Locus advocate. I'd always assumed AIX/370 and AIX PS/2
> became more available than reported here, but I left IBM before they were
> released.
>
> Enumerating factions/companies, just regarding AIX & Unix, there were the
> Federal Systems faction/company, the academic factions/company (primarily
> two factions, BSD & TCF, in Palo Alto), the PS/2 faction/company, the
> Rochester System/38->AS/400 faction/company, the Austin development lab,
> several Research locations (primarily Yorktown), ...
>
There was also AOS (Academic Operating System) which was basically
repackaged BSD 4.x ported to the IBM/RT PC[1]. At MIT's Project
Athena, most people massively preferred it to AIX, but we were force
marched to AIX by 1987 or 1988. :-/
[1] https://en.wikipedia.org/wiki/IBM_RT_PC#Software
- Ted
next prev parent reply other threads:[~2019-11-06 0:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 21:05 [TUHS] " Kevin Bowling
2019-11-03 23:29 ` Dennis Boone
2019-11-04 0:06 ` Kevin Bowling
2019-11-04 1:29 ` Dennis Boone
2019-11-04 1:58 ` Kevin Bowling
2019-11-04 3:39 ` Gregg Levine
2019-11-04 4:49 ` Kevin Bowling
2019-11-04 15:32 ` Adam Thornton
2019-11-05 16:21 ` Ronald Natalie
2019-11-05 18:04 ` Kevin Bowling
2019-11-05 19:22 ` ron
2019-11-05 17:30 ` Clem Cole
2019-11-05 18:07 ` Kevin Bowling
2019-11-05 18:15 ` Clem Cole
2019-11-05 19:03 ` Christopher Browne
2019-11-05 19:12 ` Kevin Bowling
2019-11-05 19:26 ` SPC
2019-11-05 19:28 ` SPC
2019-11-05 20:26 ` Kevin Bowling
2019-11-05 20:10 ` Clem Cole
2019-11-05 20:42 ` Kevin Bowling
2019-11-05 21:11 ` Clem Cole
2019-11-05 22:11 ` [TUHS] one element of one of M factions of N companies [Re: " Charles H Sauer
2019-11-06 0:06 ` Theodore Y. Ts'o [this message]
2019-11-06 3:36 ` Charles H. Sauer
2019-11-06 7:59 ` [TUHS] AOS and IBM/RT " SPC
2019-11-06 15:51 ` Charles H Sauer
2019-11-07 22:40 ` Grant Taylor via TUHS
2019-11-08 4:39 ` Jason Stevens
2019-11-21 6:26 ` Al Kossow
2019-11-21 11:58 ` Dan Cross
2019-11-21 13:07 ` Brad Spencer
2019-11-21 14:19 ` Dan Cross
2019-11-21 16:16 ` Chet Ramey
2019-11-21 20:53 ` Dan Cross
2019-11-21 16:43 ` greg travis
2019-11-21 19:41 ` arnold
2019-11-21 20:21 ` Jon Steinhart
2019-11-21 17:33 ` Charles H Sauer
2019-11-21 17:36 ` Dan Cross
2019-11-21 18:11 ` Brad Spencer
2019-11-21 17:29 ` Charles H Sauer
2019-11-22 20:38 ` Al Kossow
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=20191106000600.GD26959@mit.edu \
--to=tytso@mit.edu \
--cc=sauer@technologists.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).