The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: UNIX on (not quite bare) System/370
Date: Tue, 20 Dec 2022 09:31:57 +0000	[thread overview]
Message-ID: <4eZtTVIQfet1mQn895IP8V1ZHaPd_E6PAseycGIryzxcUSh-2vdyfPcB2a-KB3zyAUBYT1SPXXt200n2dBB7tt3ghyto1ZcWhQOLlqx01Mc=@protonmail.com> (raw)
In-Reply-To: <202212200856.2BK8uA1d004518@freefriends.org>

Looooots of if(n)defs in userland on "u370" in PDP-11 System V code, zilch on 3.0.1.

Yep, must've been 4.0, because that's in the first document, A.1.1: https://www.tuhs.org/Archive/Documentation/Manuals/Unix_4.0/Volume_1/A.1.1_Overview_and_Synopsis_of_Facilities.pdf

"Currently, UNIX runs on the Western Electric Co. 3B-20; Digital Equipment Corporation's (DEC) PDP-11/23, /34, /45, /70, VAX-11/780, and VAX-11/750; and IBM System/370 and equivalent."

But wait, there's more!

https://archive.org/details/unix-system-release-description-system-v

This is the Release Description released with System V.  It contains a couple of introductory documents explaining the new features and general environmental adjustments involved, as well as a number of appendices that make up the bulk of the document.  Of particular note in this case is Appendix I, the document I mentioned earlier containing a list of modification requests resolved between System III and System V.

Then there's the Documentation Guide: https://bitsavers.org/pdf/att/000-111_ATT_Documentation_Guide_Nov87.pdf

This is where mention is made of many different architectures.  There are documents for 3B20(A|S), 3B5, 3B15, 3B2, WE32100, VME/WE321SB, DEC (PDP/VAX), NS32000, M68000, iAPX 286, and Z8000.  This document also mentions docs for UNIX Real-Time-Reliable on the 3B20D.  No doubt a MERT and UNIX/RT descendant.  3B5 section mentions a "Release 5.3" so before the System V moniker.  Farthest I've seen the minor version.

I've skimmed over this listing a couple of times looking for other information but a few things stood out this time.  The WE321SB seems to be a single board computer running a version called System V/VME.  I wonder if any of those still exist, a single board running SVR2 out of the box!  No mention of System/370 though, but of course this is just a listing of available documentation at the time, it doesn't reflect what is actually out there.  Of the listed architectures, I don't think I've seen anything floating around for VME/WE321SB, Z8000, or iAPX 286, but I can't say I've looked very hard.

Needless to say the system really grew legs in the 80s even inside the Bell.

- Matt G.

------- Original Message -------
On Tuesday, December 20th, 2022 at 12:56 AM, arnold@skeeve.com <arnold@skeeve.com> wrote:


> Phil Budne phil@ultimate.com wrote:
> 
> > Is there any other surviving documentation about the system?
> > Any recall of what branch of AT&T UNIX it was based on?
> 
> 
> IIRC, in the USG 4.0 doc that I sent to Matt, it says something like
> "UNIX is an operating system for the DEC PDP-11, the DEC VAX 11/780,
> and the IBM System 370". Matt --- can you confirm? I can't get to my
> copy so easily.
> 
> That document dates from 1981, and as it came from USG, it would mean
> that the AT&T UNIX on 370 was from that world and is what is described
> in the 1984 BSTJ.
> 
> If anyone has the System III source handy, one could check if there
> is a u370 shell script and/or a u370 directory in the kernel source.
> (There used to be shell scripts named pdp11, vax, u3b, and u370 for use
> in shell 'if' statements, analogous to the C preprocessor defines.)
> If so, then UNIX 370 would date back even further.
> 
> HTH,
> 
> Arnold

  reply	other threads:[~2022-12-20  9:32 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 ` [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 [this message]
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='4eZtTVIQfet1mQn895IP8V1ZHaPd_E6PAseycGIryzxcUSh-2vdyfPcB2a-KB3zyAUBYT1SPXXt200n2dBB7tt3ghyto1ZcWhQOLlqx01Mc=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=arnold@skeeve.com \
    --cc=segaloco@protonmail.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).