The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Phil Budne <phil@ultimate.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX on (not quite bare) System/370
Date: Mon, 19 Dec 2022 20:11:46 -0700	[thread overview]
Message-ID: <CANCZdfonU=vaxtco_sRApXfCmqRjJ_4JHLFUWqAS=Ym-+F5F1g@mail.gmail.com> (raw)
In-Reply-To: <202212191738.2BJHcLBF024793@ultimate.com>

[-- Attachment #1: Type: text/plain, Size: 2693 bytes --]

On Mon, Dec 19, 2022, 10:39 AM Phil Budne <phil@ultimate.com> wrote:

> 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?
>

[ since this original question hasn't been answered ]

>
V6. There were 3 v6 ports: two interdata ports (Wollongong and Labs) and
one VM/370 port (at Harvard or Princeton). They are got to first boot the
sane year, within a few months of each other

Uts grew out of this early port. There's several blog posts about this and
the TUHS archive has the initial port that was recovered from DECtapes
recently.

https://akapugs.blog/2018/05/12/370unixpart3/ is the last in the series.

AT&T also did a V7 port, which I think is what is written up in the bell
labs journal. I'm not sure I have a proper source for this other than
comparing the two accounts. I don't know if research did this or another
group.

AT&T did the VAX port of V7 called V32,  but v32 was little more than a
swapping kernel that didn't do demand paging. This is where the Berkeley
folks started to do paging with 3BSD. It is also where AT&T did their Vax
port that other mailing list threads chronicled.

Warner

>

[-- Attachment #2: Type: text/html, Size: 4588 bytes --]

  parent reply	other threads:[~2022-12-20  3:13 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 17:38 [TUHS] " Phil Budne
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 ` Warner Losh [this message]
2022-12-20  8:56 ` [TUHS] Re: UNIX on (not quite bare) System/370 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
2022-12-20 22:25 Noel Chiappa
2022-12-20 23:18 ` Bakul Shah
2022-12-22 17:26 Noel Chiappa
2022-12-22 17:33 ` Dan Cross
2022-12-22 20:25 ` Warner Losh
2022-12-22 23:06   ` Warner Losh

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='CANCZdfonU=vaxtco_sRApXfCmqRjJ_4JHLFUWqAS=Ym-+F5F1g@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=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).