From: Jonathan Gray <jsg@jsg.id.au>
To: arnold@skeeve.com
Cc: segaloco@protonmail.com, tuhs@tuhs.org
Subject: [TUHS] Re: UNIX on (not quite bare) System/370
Date: Tue, 20 Dec 2022 20:55:15 +1100 [thread overview]
Message-ID: <Y6GGgy1xTTduoSBJ@largo.jsg.id.au> (raw)
In-Reply-To: <202212200939.2BK9dqpo011090@freefriends.org>
On Tue, Dec 20, 2022 at 02:39:52AM -0700, arnold@skeeve.com wrote:
> segaloco <segaloco@protonmail.com> wrote:
>
> > 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."
>
> So there we have it, Unix/370 inside the Bell System was at 4.0. I don't think they ever released that
> outside the Bell System. Not surprising, as it needed a modified TSS underneath.
>
> Arnold
"A Bell Laboratories -wide reorganisation in January 1981 resulted in
the UNIX Lab being renumbered. Release 4.0 was launched from this
organization in March. It introduced new IPC mechanisms as well as new
drivers and changes to the text processing software and the C libraries
etc. Also in March, the first UNIX release for an IBM machine was
launched as UNIX/370 Release 3.0"
Pirzada, A Statistical Examination of The Evolution of the UNIX System
https://spiral.imperial.ac.uk/bitstream/10044/1/7942/1/Shamim_Sharfuddin_Pirzada-1988-PhD-Thesis.pdf
next prev parent reply other threads:[~2022-12-20 9:55 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
2022-12-20 9:39 ` arnold
2022-12-20 9:55 ` Jonathan Gray [this message]
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=Y6GGgy1xTTduoSBJ@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--cc=arnold@skeeve.com \
--cc=segaloco@protonmail.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).