From: Kevin Bowling <kevin.bowling@kev009.com>
To: SPC <spedraja@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Amdahl UTS, AIX/370, AIX/ESA
Date: Tue, 5 Nov 2019 13:26:56 -0700 [thread overview]
Message-ID: <CAK7dMtCEgXNHpForW+C+sOKsTi8LypeBkAZpfSH5aE-LEYvHsQ@mail.gmail.com> (raw)
In-Reply-To: <CACytpF_gyyLggNOkRFGXXcodSQLvh7u4pfK0mrPHpv7Yst1z-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
Yup I was involved in the salvage and was the first purveyor of these
floppies to the modern internet. Saying this as it is germane to my
original post in the thread, I have a lot of experience doing this kind of
thing and I need willing connections to the source materials in question.
Regards,
Kevin
On Tue, Nov 5, 2019 at 12:28 PM SPC <spedraja@gmail.com> wrote:
> Uh... "veras algo" means "years ago". My apologies.
>
> El mar., 5 nov. 2019 20:26, SPC <spedraja@gmail.com> escribió:
>
>>
>>
>> El mar., 5 nov. 2019 20:12, Kevin Bowling <kevin.bowling@kev009.com>
>> escribió:
>>
>>> It was used in academia although it did appear elsewhere for instance in
>>> some PLC applications, for a long while some supertankers were running
>>> PS/2s with Optio22 I/O boards to control pumps and whatnot.
>>>
>>
>> It's available as diskette images on Internet from veras algo. But it can
>> be installed and run mostly for cause of the advance in the virtualization
>> applications, together with some specific efforts of investigation and
>> testing.
>>
>> And yes, we used SCO for our PS/2 servers running Unix or Unix-like. No
>> discussion, at least until some years after when I installed one RS/6000
>> server with AIX 3.2
>>
>> Regards
>> Sergio
>>
>
[-- Attachment #2: Type: text/html, Size: 2422 bytes --]
next prev parent reply other threads:[~2019-11-05 20:27 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 [this message]
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=CAK7dMtCEgXNHpForW+C+sOKsTi8LypeBkAZpfSH5aE-LEYvHsQ@mail.gmail.com \
--to=kevin.bowling@kev009.com \
--cc=spedraja@gmail.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).