The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kevin Bowling <kevin.bowling@kev009.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Amdahl UTS, AIX/370, AIX/ESA
Date: Tue, 5 Nov 2019 13:42:37 -0700	[thread overview]
Message-ID: <CAK7dMtC=P6pCL9ac0YGLZ=p_bFVqNdAT9wmaEeC7hebLauXC4Q@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2ORG2Yrg06HC-8Bhihe1fB6zuXBzSg9a9CGhT04d39=OQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3787 bytes --]

Clem,

I am very curious about this UNIX for OS/400 work it sounds either
different or much earlier than what I am familiar with.  I am familiar with
the PASE environment that shipped around OS/400 V4R4 (1999?).  After
AS/400s started running PowerPCish CPUs (there is a bit of history there I
won't dive into) PASE was like WINE for Linux.. same CPU arch, do some
library and linker/loader tricks to hoist a different (AIX 4.3 first)
environment within OS/400s understanding of the universe.  A year or so
later, some very bright group figured to use the OS/400's Single Level
Store as the device model/device virtualization for the CPU virtualization
(LPAR) in later POWER CPUs.  You could run Linux or OS/400 or AIX this
way.  That work was then somewhat inverted, and pHyp was born from the
OS/400's SILC idea of machine dependent code as a light weight firmware
hypervisor in the converging iSeries and pSeries POWER systems.. they
switched the device model/device virtualization to AIX called APV or
PowerVM.

It was nicknamed "Fortress Rochester" for a reason.  They did some very
nice work.  But yeah IBM was running 4 large and extremely different
computing businesses in the 1990s and probably some smaller ones too.  They
were very different but the systems did interoperate pretty well given the
stakes.

Regards,
Kevin

On Tue, Nov 5, 2019 at 1:10 PM Clem Cole <clemc@ccc.com> wrote:

>
>
> On Tue, Nov 5, 2019 at 2:03 PM Christopher Browne <cbbrowne@gmail.com>
> wrote:
>
>> The dates seem to decently explain the invisibility; introduction in 1992
>>
> The formal introduction of the PS/2 was April 87 (by the crew of Mash for
> the TV ads IIRC).  Again, if my memory serves LCC started working on UNIX
> for the 370 in the mid'86s, actually before the PS/2 was announced, which
> would be announced as AIX/370.   ISC had done the original 386 port for
> Intel, IBM, and AT&T - but that was for an ISA based systems originally
> [Phil Shevrin pulled one of the best sales jobs I ever knew -- he got paid
> three times for the same basic work].
>
> At some point (and I would have to ask someone like Bruce Walker or Greg
> Thiel for the better info), the contract got widen AIX to include the PS/2
> - a.k.a. create AIX/386.  How much of the original ISC work was that build
> upon, I never knew.
>
> LCC worked for a number of years and the two AIX's were available for
> customers, probably under a special University license.   The formal
> introduction was later (and '92 sounds right). But there were sites that
> had one or both before that time.   I want to say, LCC worked with IBM for
> about 8-10 years starting in the mid-80s. BTW: They also did a UNIX port to
> AS/400 (on top of the native OS - similar to Eunice for the VAX or
> today's MingWin and Dave Korn's UWIN stuff).   I've forgotten the dates on
> that, I want to say 93/94 time frame.
>
> Enough time has gone by, I think I can safely tell another story, WRT the
> AS/400.  When that happened, IBM and LCC had a number oif years under their
> bridge and the LCC management team thought we knew how to work with IBM.
> Since we had a base IBM contract, we all figured that could be
> added/amended to as needed.  When the folks from Rochester called asking
> about a quote for the AS/400 work, our sales folks trotted out the existing
> contract for AIX and figured - ok write a new SOW and we are done.   Nope
> -- different division/different set of lawyers.  Something was said to us
> in the form of 'Rochester Won the Baldridge Award.'   I remember our CEO
> groaning - and saying something like 'Here we go again.'  It was then I
> realized IBM was N different companies, each competing with each other.
>
> Clem
> ᐧ
>

[-- Attachment #2: Type: text/html, Size: 5941 bytes --]

  reply	other threads:[~2019-11-05 20:43 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-03 21:05 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 [this message]
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
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='CAK7dMtC=P6pCL9ac0YGLZ=p_bFVqNdAT9wmaEeC7hebLauXC4Q@mail.gmail.com' \
    --to=kevin.bowling@kev009.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@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).