The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kevin Bowling <kevin.bowling@kev009.com>
To: Ronald Natalie <ron@ronnatalie.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Amdahl UTS, AIX/370, AIX/ESA
Date: Tue, 5 Nov 2019 11:04:09 -0700	[thread overview]
Message-ID: <CAK7dMtBQH=58m_-O0uGDQAhEuOfr+nhAnTxik8EY9PJ=cS7r3w@mail.gmail.com> (raw)
In-Reply-To: <8C50B42C-CDF9-47FE-B2D7-AB980C059099@ronnatalie.com>

Veering off topic but I'm familiar with the Wizard
http://ps-2.kev009.com/ohlandl/CPU/wizard.html

What was the framebuffer used for/under?

The HFT and LFT terms were carried forth into POWER AIX.  AIX 3.x had
a home grown HFT with virtual terminals and some other semi-graphical
features.  AIX 4.X ported a STREAMs based console I/O stack from OSF
and they called it the LFT because it lost all those features; users
were directed to X11 for advanced terminal handling.

Regards,
Kevin

On Tue, Nov 5, 2019 at 9:21 AM Ronald Natalie <ron@ronnatalie.com> wrote:
>
> One of my first jobs I did for the company that I ended up working for decades was a job for IBM FSD to put a second ethernet interface in to “secure XENIX” (a MLS system) to allow the system to be  used for downgrading classified material.    This gave us an in with IBM FSD and this led to us doing work with an IBM on a pair of microchannel i860 coprocessor cards called the Wizard and the W4.   We ported AIX to both of them.    The cards ran inside of another AIX PS/2 system so the TCF was really handy in allowing apps that only had 386 versions to run, the ability to maintain a common file system, and to share peripherals.   Indeed, I think the major reason IBM used the TCF concept is it gave the 370 version of the thing an easy way to interoperate with user’s on the PS/2’s.   3270’s and other terminals designed for the mainframe really weren’t suited for UNIX.
>
> The initial Wizard card had no I/O other than the host PS/2.    It was really more or less an academic experiment (the cards were also buggy).    Two amusing things however came out of that port.   The AIX for the PS/2 had this thing to multiplex the normal VGA display (outside of X) called the “High Function Terminal.”   Our i860 version was less capable so it was denoted the “Low Function Terminal.”     The other was that I hacked the -mm macro package to mimic the style of the IBM manuals so we could write “IBM-ish” documentation.
>
> The W4 card was interesting.   It had 4 i860 processors along with it’s own framebuffer.    One of my employees spent a lot of time of in Owego fixing the memory system (the whole thing was set up with these Xilinx PGAs that were easy to update in the field).     Amusingly, the machine-specific parts of the W4 version of the AIX kernel had more in common with the 370 version than the i386 version.     I spent weeks out at the IBM Palo Alto Science Center doing work on this project.    I had managed to inadvertantly shutdown the main AIX/370 in the cluster (such is a problem when things get too transparent).     Of course, while I had experience using VM/CMS before (both at the University of Maryalnd and at Rutgers), I’d never really much dealt with the operations side of the 370.    But I found my way to a 3270 and typed “ipl aix” with at the command line with extreme optimism, but that was indeed all it took.
>
>

  reply	other threads:[~2019-11-05 18:04 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 [this message]
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
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='CAK7dMtBQH=58m_-O0uGDQAhEuOfr+nhAnTxik8EY9PJ=cS7r3w@mail.gmail.com' \
    --to=kevin.bowling@kev009.com \
    --cc=ron@ronnatalie.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).