From: Phil Budne <phil@ultimate.com>
To: tuhs@tuhs.org
Subject: [TUHS] UNIX on (not quite bare) System/370
Date: Mon, 19 Dec 2022 12:38:21 -0500 [thread overview]
Message-ID: <202212191738.2BJHcLBF024793@ultimate.com> (raw)
The October 1984 BSTJ article by Felton, Miller and Milner
https://www.bell-labs.com/usr/dmr/www/otherports/ibm.pdf
Describes an AT&T port of UNIX to System/370 using TSS/370
underpinnings as the "Resident System Supervisor" and used as the 5ESS
switching system development environment.
I also found mention at http://www.columbia.edu/~rh120/ch106.x09
chapter 9 of http://www.columbia.edu/~rh120/ with footnote 96:
Ian Johnstone, who had been the tutor at University of New
South Wales working with Professor John Lions, was one of the
researchers invited to Bell Labs. He managed the completion at
AT&T Bell Labs of the port of Unix to the IBM 370 computer. See
"Unix on Big Iron" by Ian Johnstone and Steve Rosenthal, UNIX
Review, October, 1984, p. 26. Johnstone also led the group that did
the port to the AT&T 2B20A multiprocessor system.
I found
https://ia902801.us.archive.org/3/items/Unix_Review_1984_Oct.pdf/Unix_Review_1984_Oct.pdf
"BIG UNIX: The Whys and Wherefores" (pdf p.24), which only offers rationale.
Also:
"IBM's own involvement in Unix can be dated to 1979, when it
assisted Bell Labs in doing its own Unix port to the 370 (to
be used as a build host for the 5ESS switch's software). In
the process, IBM made modifications to the TSS/370 hypervisor
to better support Unix.[12]"
at https://en.wikipedia.org/wiki/IBM_AIX#cite_ref-att-s370-unix_12-0
Is there any other surviving documentation about the system?
Any recall of what branch of AT&T UNIX it was based on?
Thanks!
Phil
next reply other threads:[~2022-12-19 17:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 17:38 Phil Budne [this message]
2022-12-19 18:53 ` [TUHS] " segaloco via TUHS
2022-12-19 21:01 ` Clem Cole
2022-12-19 21:19 ` Rob Pike
2022-12-19 22:15 ` segaloco via TUHS
2022-12-20 0:02 ` Brad Spencer
2022-12-20 1:04 ` Adam Thornton
2022-12-20 2:35 ` segaloco via TUHS
2022-12-20 14:25 ` Andrew Hume
2022-12-19 23:02 ` Clem Cole
2022-12-20 1:20 ` Larry Stewart
2022-12-20 1:33 ` Larry McVoy
2022-12-20 1:57 ` George Michaelson
2022-12-20 2:06 ` Dan Cross
2022-12-20 15:04 ` Chet Ramey
2022-12-20 2:12 ` Adam Thornton
2022-12-20 15:29 ` Andy Kosela
2022-12-20 15:35 ` Adam Thornton
2022-12-21 2:43 ` Luther Johnson
2022-12-20 23:18 ` David Arnold
2022-12-20 2:52 ` Bakul Shah
2022-12-20 3:09 ` Larry McVoy
2022-12-20 3:27 ` Bakul Shah
2022-12-20 3:48 ` Warner Losh
2022-12-20 4:21 ` Jonathan Gray
2022-12-19 21:36 ` Marc Donner
2022-12-19 22:52 ` Charles H Sauer (he/him)
[not found] ` <01428a75-3507-7b8a-fd35-cef74c8c0bd2@ucsb.edu>
2022-12-20 1:49 ` [TUHS] Re: pre-1991 USENIX proceedings Marc Donner
2022-12-20 3:11 ` [TUHS] Re: UNIX on (not quite bare) System/370 Warner Losh
2022-12-20 8:56 ` arnold
2022-12-20 9:31 ` segaloco via TUHS
2022-12-20 9:39 ` arnold
2022-12-20 9:55 ` Jonathan Gray
2022-12-20 14:27 ` Clem Cole
2022-12-23 1:53 ` Rob Gingell
2022-12-22 19:00 ` Andrew Hume
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=202212191738.2BJHcLBF024793@ultimate.com \
--to=phil@ultimate.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).