The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Un-released/internal/special UNIX versions/ports during the years?
Date: Wed, 1 Mar 2017 13:17:00 -0500	[thread overview]
Message-ID: <CAC20D2PaauHUHgOk0XsTtNvVoAijn=cWxm9vv9EPvOi_PbTbiw@mail.gmail.com> (raw)
In-Reply-To: <D7FABA1E-4897-42F3-A5BD-4D82D6770558@ronnatalie.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3502 bytes --]

On Wed, Mar 1, 2017 at 2:45 AM, Ronald Natalie <ron at ronnatalie.com> wrote:

> AIX/370 was a real product.

​Indeed​ it was.




>   All of these AIX versions came from the same source code and used the
> IBM TCF to allow you to transparently run executables across nodes in the
> cluster.

​Exactly right.   TCF - Transparent Computing Facility -- No mean trick...
​you can mix PS/2 and 370 in the cluster, so root on desk allowed me root
on the mainframe too.   What was cool was that the TCF will look at the
executable and find the proper CPU.   The big mistake was that that node id
was stored in a single 32 bit word and assigned per bit, which was a
scaling issues.

I was at Locus Computing Corp (aka LCC or just "Locus"), who developed AIX
for IBM under contract and TCF was part of it.  The direct result of the The
LOCUS Distributed System Architecture
<https://www.amazon.com/Distributed-System-Architecture-Computer-Systems/dp/0262517191/ref=sr_1_1?s=books&ie=UTF8&qid=1488391384&sr=1-1&refinements=p_27%3AGerald+J.+Popek>
from
UCLA.  The book actually describes much of the AIX/370 work, but starts
with the original UCLA work.  I did not work on the IBM project, although a
number of my peers did.  I was higher to help developed TNC - Transparent
Network Computing, which is was used in Intel's Paragon and DEC's
TruClusters and a never shipped HP Cluster Product. Many of the same ideas
but we wanted a separate team that never saw the IBM code so there could
never be any concern about ownership.  The architects like me and Roman,
were allowed to talk to the AIX architects, such as Bruce; but we keep
separate development environments at separate sites.    After the IBM work
ended, all of the Locus  distributed system folks the struct around went to
work on TNC and the technology go sold off and licensed.   What was
interesting is that TNC was open'ed sourced after the Compaq/HP mergers and
put into Linux but I've forgotten the URL (I'll search and follow up).

It's a real shame it never went anywhere.   It was a very, very cool.




>      The only AIX that didn’t play was the completely independent (and in
> my opinion somewhat brain damaged) IBM/RT UNIX.    If there was a TCF-based
> RT kernel, I never saw it, even inside the IBM labs.

​That was IBM politics.   LCC has the contract for the original AIX port to
the 370.   When the RT was developed, the Austin team was ramped up.   One
of our members of the TUHS list who is remaining silent I see is not saying
why but I know was there ;-) and might  known the actual politics, I never
did.   But when the AIX/RT port was forked, they started with AIX/370 code
base and removed the TCF code.   But LCC still had the AIX/370 contract
from Enterprise system group to maintain AIX/370.   And also, Locus had the
contract from Entry Systems, who all they wanted TCF.   So AIX/386 and
AIX/370 as Ron points out were one code base, one dev team (at LCC in
California).

Dan Cross said:  "I had understood was that AIX/370 was actually OSF/1
based"

It maybe that by the end, the user space was based on the OSF/1 user space
code.  That was true for HP and DEC also.   But I can definitely state
AIX/370 and AIX/386 were one set of source trees and all of was done by
Locus Computing Corporation certainly through the mid 1990s.

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170301/f5d0beb0/attachment-0001.html>


  parent reply	other threads:[~2017-03-01 18:17 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25 14:17 Arno Griffioen
2017-02-25 14:32 ` Larry McVoy
2017-02-25 16:35   ` Steve Nickolas
2017-02-25 18:11     ` Joerg Schilling
2017-02-25 18:16       ` Brantley Coile
2017-02-25 17:31   ` Clem Cole
2017-02-25 17:34     ` Charles Anthony
2017-02-25 17:36     ` Brantley Coile
2017-02-25 18:28     ` Tim Bradshaw
2017-02-27  5:08       ` Dave Horsfall
2017-02-25 17:40   ` Nemo
2017-02-25 17:43     ` Brantley Coile
2017-02-25 23:23   ` Dave Horsfall
2017-02-26 12:39     ` Noel Chiappa
2017-02-26 12:46       ` [TUHS] The size of EMACS, and what hides in kLOCs Michael Kjörling
2017-02-26 16:05         ` Nemo
2017-02-26 17:05           ` Michael Kjörling
2017-02-26 18:23             ` Tim Bradshaw
2017-02-26 19:19               ` Jim Carpenter
2017-02-26 19:39                 ` [TUHS] EMACS movemail suid root bug Michael Kjörling
     [not found]           ` <CALMnNGg3dRV0yPV1GgeqaOFG0Mb5PSNuqgPs8pLKOHYzurYEOg@mail.gmail.com>
2017-02-27  1:00             ` [TUHS] The size of EMACS, and what hides in kLOCs Nemo
2017-02-27  1:48               ` Steve Nickolas
2017-02-27  8:26                 ` Michael Kjörling
2017-02-27  1:19           ` Jason Stevens
2017-02-27  2:13             ` Nick Downing
2017-02-26 13:32       ` [TUHS] Un-released/internal/special UNIX versions/ports during the years? Tim Bradshaw
2017-02-26 14:19         ` Michael Kerpan
2017-02-26 14:54           ` Joerg Schilling
2017-02-26 15:25             ` Angelo Papenhoff
2017-02-26 15:55               ` Joerg Schilling
2017-02-26 15:37             ` Tim Bradshaw
2017-02-26 15:52               ` Joerg Schilling
2017-02-26 16:06                 ` tfb
2017-02-26 16:27                   ` Ron Natalie
2017-02-26 18:32                     ` Lars Brinkhoff
2017-02-27 16:04                       ` Tony Finch
2017-02-27 23:51                         ` Nick Downing
2017-02-26 16:22                 ` Michael Kerpan
2017-02-26 16:36                   ` Ron Natalie
2017-02-26 18:01                     ` William Pechter
2017-02-26 18:40               ` Lars Brinkhoff
2017-02-26 16:06           ` Tim Bradshaw
2017-02-26 16:30             ` Ron Natalie
2017-02-26 17:15           ` Ron Natalie
2017-02-26 17:20             ` Michael Kjörling
2017-02-26 17:23               ` Ron Natalie
2017-02-26 17:33               ` Steve Nickolas
2017-02-26 17:39                 ` Michael Kjörling
2017-02-26 17:39                 ` Michael Kerpan
2017-02-26 19:33                   ` [TUHS] roff Larry McVoy
2017-02-26 19:34                     ` Ron Natalie
2017-02-26 19:36                       ` Ron Natalie
2017-02-26 19:46                         ` Dan Cross
2017-02-26 19:41                     ` Michael Kerpan
2017-02-26 21:27                       ` Joerg Schilling
2017-02-26 21:28                         ` Joerg Schilling
2017-02-27 13:59                         ` Steffen Nurpmeso
2017-02-28 20:15       ` [TUHS] Un-released/internal/special UNIX versions/ports during the years? Dave Horsfall
2017-02-28 20:22         ` Lars Brinkhoff
2017-03-01  1:31           ` Dave Horsfall
2017-02-28 20:40         ` Jaap Akkerhuis
2017-03-01 12:45           ` Michael Kjörling
2017-02-25 14:44 ` [TUHS] Un-released/internal/special UNIX versions/ports during theyears? jsteve
2017-02-25 19:02 ` [TUHS] Un-released/internal/special UNIX versions/ports during the years? Al Kossow
2017-02-26  4:06   ` Jason Stevens
2017-03-01  4:15 ` Gregg Levine
2017-03-01  7:17   ` arnold
2017-03-01  7:45   ` Ronald Natalie
2017-03-01 11:14     ` [TUHS] Un-released/internal/special UNIX versions/ports duringthe years? jsteve
2017-03-01 14:54     ` [TUHS] Un-released/internal/special UNIX versions/ports during the years? Dan Cross
2017-03-01 15:41     ` Nemo
2017-03-01 18:17     ` Clem Cole [this message]
2017-03-02  2:13       ` Jason Stevens
2017-03-02  2:27       ` Gregg Levine

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='CAC20D2PaauHUHgOk0XsTtNvVoAijn=cWxm9vv9EPvOi_PbTbiw@mail.gmail.com' \
    --to=clemc@ccc.com \
    /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).