The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jsteve@superglobalmegacorp.com (jsteve@superglobalmegacorp.com)
Subject: [TUHS] Un-released/internal/special UNIX versions/ports duringthe years?
Date: Wed, 1 Mar 2017 19:14:12 +0800	[thread overview]
Message-ID: <558c0a18-c601-4698-903f-a12ed75d5053@HK2APC01FT021.eop-APC01.prod.protection.outlook.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: 3299 bytes --]

I had never hear of an i860 board from IBM, but a little searching, and it almost looks like it was going to be a thing.

NUMBER     290-817
DATE       901218
TYPE       Programming
TITLE      INTEL OS/2 AND AIX I860 SOFTWARE DEVELOPMENT TOOLS FOR C AND FORTRAN
ABSTRACT  Today, IBM announces C and FORTRAN compiler support for the
   PS/2 (R) Wizard Adapter running under both AIX (R) PS/2 and OS/2 (R)
   operating systems.
<           hundreds of lines of information deleted          >
TECHINFO   TECHNICAL INFORMATION
   SPECIFIED OPERATING ENVIRONMENT
v  MACHINE REQUIREMENTS:
|  o   The Intel OS/2 and AIX i860 Software Development Tools for C and
|      FORTRAN require one of the following PS/2 system units:
|      -   PS/2 Model 70
|      -   PS/2 Model P75*
|      -   PS/2 Model 80
|      -   PS/2 Model 90 XP*
|      -   PS/2 Model 95 XP*
|             The Model P70 is not supported.
====>  *  These models are not currently supported by AIX PS/2.
          Therefore, the PS/2 Wizard Adapter will operate only with IBM
          OS/2 on these models.


Or later something like this:

IBM architecture - RT
IBM architecture - RS/6000
IBM architecture - S/370
Intel architecture - i386

(rumors of)
Intel architecture - i860	(Wizard PS/2 cardset with 4xi860)
whatever comes out of Steve Chen's supercomputer work

Of course, with IBM not licensing AIX source to anyone, these are only
IBM machines, but that is not the same as AIX being a non-portable OS.

Rumors are that IBM's customers are pressing very hard for source
licenses and that someday such licenses will be available.  Whether
that would lead to ports to other machines, I can't predict.


Very interesting!

Sent from Mail for Windows 10

From: Ronald Natalie
Sent: Wednesday, 1 March 2017 3:45 PM
To: Gregg Levine
Cc: Tuhs
Subject: Re: [TUHS] Un-released/internal/special UNIX versions/ports duringthe years?


> On Feb 28, 2017, at 10:15 PM, Gregg Levine <gregg.drwho8 at gmail.com> wrote:
> 
> Hello!
> We (well most of us) all of us know about AIX. Well what about AIX/370?
> ——

AIX/370 was a real product.     One of the ones that I don’t ever think saw the light of day was the i860 AIX port.   IBM made two i860 add-in cards for the PS/2.   The single processor version was called the Wizard and there was a 4 processor version with an integral frame buffer called the W4.     We ported AIX to both.    The i860 version actually had more in common with the 370 version than it did with the 386.     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.     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.

Speaking of odd job control mechanisms.   The 386 side had a device that multiplexed the PS/2 console into multiple streams called the “High Function Terminal.”   When we wrote the virtual console for the Wizard/W4 add in card, we called it the “Low Function Terminal."

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


  reply	other threads:[~2017-03-01 11:14 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25 14:17 [TUHS] Un-released/internal/special UNIX versions/ports during the years? 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     ` jsteve [this message]
2017-03-01 14:54     ` Dan Cross
2017-03-01 15:41     ` Nemo
2017-03-01 18:17     ` Clem Cole
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=558c0a18-c601-4698-903f-a12ed75d5053@HK2APC01FT021.eop-APC01.prod.protection.outlook.com \
    --to=jsteve@superglobalmegacorp.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).