From: arnold@skeeve.com (arnold@skeeve.com)
Subject: [TUHS] UNIX on S/370
Date: Sun, 19 Nov 2017 20:50:48 -0700 [thread overview]
Message-ID: <201711200350.vAK3omwQ013495@freefriends.org> (raw)
In-Reply-To: <CAJfiPzxnwNdAHLRV4+QUF-k-ib4tuFj5BLy-r-jL9W7zHHziQw@mail.gmail.com>
Nemo <cym224 at gmail.com> wrote:
> Recent commentary on porting led me to read the article on porting
> UNIX to S/370 (https://www.bell-labs.com/usr/dmr/www/otherports/ibm.pdf)
> to support 5ESS development because the existing PDP11s were being
> overwhelmed. I confess to not having this read this before and find
> it interesting. Any recollections from anyone on the matter. And
> whatever happened to it?
>
> N.
That article (as noted) was originally published in the Bell System
Technical Journal special issue on UNIX.
The System III manuals say something like "UNIX is an operating system
for DEC PDP-11, Vax 11/780 and IBM S/370 computers" so at least within
the Bell System, the S/370 was supported.
It does not seem to have been released to the world, which is a shame;
it may be because of the underlying I/O supervisor which was a modified
IBM OS.
Arnold
next prev parent reply other threads:[~2017-11-20 3:50 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 0:57 Nemo
2017-11-20 1:01 ` Ronald Natalie
2017-11-20 1:06 ` Dave Horsfall
2017-11-20 3:50 ` arnold [this message]
2017-11-20 15:23 ` Clem Cole
2017-11-20 16:03 ` ron minnich
2017-11-20 16:31 ` Clem Cole
2017-11-20 19:44 ` Paul Winalski
2017-11-20 19:56 ` Larry McVoy
2017-11-20 23:43 ` Ron Natalie
2017-11-20 23:45 ` Larry McVoy
2017-11-20 23:49 ` Ron Natalie
[not found] ` <CAC20D2N=aBhdON1YqHH57ZG-TmC62yWGF4_=HK5Gp2XwdbHkyQ@mail.gmail.com>
2017-11-21 2:41 ` Larry McVoy
2017-11-29 22:42 ` Dave Horsfall
2017-11-29 22:55 ` ron minnich
2017-11-21 1:15 ` Ron Natalie
2017-11-21 3:29 ` Grant Taylor
2017-11-21 3:40 ` Ron Natalie
2017-11-21 3:46 ` Grant Taylor
2017-11-21 8:09 ` arnold
2017-11-21 16:49 ` Paul Winalski
2017-11-21 4:34 ` Clem cole
2017-11-21 5:42 ` Grant Taylor
2017-11-21 12:00 ` Ron Natalie
2017-11-21 13:51 ` Clem Cole
2017-11-21 14:59 ` Larry McVoy
2017-11-21 17:06 ` Clem Cole
2017-11-21 17:23 ` Clem Cole
2017-11-21 18:29 ` Larry McVoy
2017-11-21 19:10 ` Clem Cole
2017-11-21 15:40 ` Ron Natalie
2017-11-21 15:45 ` Larry McVoy
2017-11-21 13:24 ` Clem Cole
2017-11-22 1:33 ` Kevin Bowling
2017-11-22 6:35 ` Wesley Parish
2017-11-22 9:38 ` Kevin Bowling
2017-11-22 13:40 ` Clem Cole
2017-11-22 14:09 ` Ron Natalie
2017-11-22 13:51 ` Clem Cole
2017-11-22 14:04 ` Ron Natalie
2017-11-20 16:05 Noel Chiappa
2017-11-20 16:37 ` Clem Cole
2017-11-20 16:47 ` Charles H Sauer
2017-11-20 17:44 ` Toby Thain
2017-11-20 19:07 ` Paul Winalski
2017-11-20 19:10 ` Larry McVoy
2017-11-20 19:36 ` Warner Losh
2017-11-20 19:36 ` Larry McVoy
2017-11-20 19:39 ` Larry McVoy
2017-11-20 19:56 ` Arthur Krewat
2017-11-20 19:59 ` Larry McVoy
2017-11-20 19:27 ` arnold
2017-11-20 19:29 ` Larry McVoy
2017-11-20 22:56 ` Michael Parson
2017-11-20 23:23 ` Larry McVoy
2017-11-21 2:56 Noel Chiappa
2017-11-21 3:15 ` Ron Natalie
2017-11-21 3:51 ` Larry McVoy
2017-11-21 5:14 ` Warner Losh
2017-11-21 5:20 ` Larry McVoy
2017-11-22 15:38 Noel Chiappa
2017-11-28 0:13 ` Kevin Bowling
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=201711200350.vAK3omwQ013495@freefriends.org \
--to=arnold@skeeve.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).