The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX on (not quite bare) System/370
Date: Thu, 22 Dec 2022 13:25:11 -0700	[thread overview]
Message-ID: <CANCZdfq=H4zCW=FSYkZNfLxapAuFAm9ttL54GnB2=5f0WEz+uw@mail.gmail.com> (raw)
In-Reply-To: <20221222172654.965D618C079@mercury.lcs.mit.edu>

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

On Thu, Dec 22, 2022, 10:27 AM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:

>     > From: Bakul Shah
>
>     > There is a further para:
>
>     >  Reducing external memory fragmentation to zero by utilizing the VAX-
>     >  11/780 memory mapping hardware for scatter loading is high on the
> list
>     >  of things to do in the second implementation pass.
>
> I'm curious as to exactly what is meant by "external memory"? They must
> mean
> memory on the Synchronous Backplane Interconnect:
>
>   http://gunkies.org/wiki/Synchronous_Backplane_Interconnect
>
> I.e. what most of us would call 'main memory'.
>
> If this code didn't even allocate main memory by pages, instead of in
> process-size blocks, it sounds like it's much like 32V (or is it 32V that's
> being discussed; I thought this thread had moved on to the Reiser demand
> paging version - my apologies it I've gotten lost).
>
>
> Also, this note:
>
>   http://gunkies.org/wiki/Talk:CB-UNIX
>
> from Dale DeJager (which he kindly gave me permission to post)


It's quite similar to a note he posted to I think unix-wizards mailing list
back in the late 80s. I found it for my early unix talk and it's why I call
cbunix the first fork.

gives a fair
> amount of detail on the relationship between the Research and CB/UNIX
> versions, with a brief mention of USG - precisely the era, and
> relationships,
> that are so poorly documented. Interestingly, he indicates that the early
> versions of what later became CB/UNIX used something in the V1/V3 range (V4
> was the first one in C), so it dates back earlier than most people
> apparently
> assume.
>

For my early unix talk, I think I pegged that at V2. Running on the 11/20
coupled with V3 manual strongly suggesting running on 11/20 would be better
with v1 or v2.

If anyone else has any first-hand notes (i.e.from people who were there at
> the
> time), about the relationship between all the early systems, for which the
> author has given permiosssion to post it, please send it to me and I will
> add it to the appropriate article on the CHWiki
>

The source I had said it was NJ Bell that did the productization of v2 in
1972 or 1973 for the SCCS project. I have a memory of reading somewhere
that Columbus took over maintenance once they deployed and out of that grew
cbunix. I'll see if I can find that again. It matches other things I've
read that Columbus provided support for the operating companies deploying
unix.

Warner

Probably the most needed is more about the roots of USG; Dale has filled in
> CB/UNIX, and the roots of PWB are covered fairly well in the BSTJ article
> on it:
>
>   https://archive.org/details/bstj57-6-2177
>
> at least, for PWB1. Anything that covers the later PWBs would likewise be
> gratefully receied.
>
>
> I suppose I should also write up the relationships of the later UNIXen -
> 32V
> and its descendants too - any material sent to me about them will be most
> gratefully received. (If anyone want a CHWiki account, to write it up
> themselves, please let me know).
>
>    Noel
>

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

  parent reply	other threads:[~2022-12-22 20:26 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 17:26 Noel Chiappa
2022-12-22 17:33 ` Dan Cross
2022-12-22 20:25 ` Warner Losh [this message]
2022-12-22 23:06   ` Warner Losh
  -- strict thread matches above, loose matches on Subject: below --
2022-12-20 22:25 Noel Chiappa
2022-12-20 23:18 ` Bakul Shah
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)
2022-12-20  3:11 ` 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='CANCZdfq=H4zCW=FSYkZNfLxapAuFAm9ttL54GnB2=5f0WEz+uw@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).