The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Richard Salz <rich.salz@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Paul Ruizendaal <pnr@planet.nl>
Subject: Re: [TUHS] 32V memory management: not quite V7 style swapping -- source code update
Date: Sun, 6 Jun 2021 15:02:56 -0400	[thread overview]
Message-ID: <CAC20D2Nbxce2dcZAfQQpMzbJ-2g_wpK3BJbkx+Lhh4j4imaYYw@mail.gmail.com> (raw)
In-Reply-To: <CAFH29trpSQB-rqfLOuzgs=xxRSs-BRt67+iZrk1sK9DZL8SB0g@mail.gmail.com>

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

Yes -- this is what I just sent to Larry on  private exchange.

The BSD release order - 3.0 BSD is the replacement for 32V, 4.0 is the
first real update and 4.1 was the so-called 'FASTVAX' stuff Joy did as part
of the UNIX/VMS bake off with Stanford.  4.0 and 4.1 are very similar.
 4.1 lived 'in the wild' about 3-4 years as the standard 'BSD' and any one
with Vax (certainly at a university) got the BSD tape.  That is the code
base that Rob Gurwitz used to write the original BBN TCP -- which did not
use open (/dev/ip  /dev/tcp/hostname or /dev/udp/hostname) like MIT's
ChaosNet.

4.1a was Bill's first attempt at rewriting Gurwitz's code and creating
sockets.   Only a few people had it (I was one) - but it did make it to a
number of the IETF beta testers -- the MIT folk I know had the tape - Noel
might know whom there they had it.   4.1b replaced that about 3-6 months
later but I'm not sure it left UCB very far -- I ran it on one of the CAD
machines as 4.1c was being created.  IIRC B was the first to have Kirks FFS
in it and we were pushing the FFS code with our cad programs that beat on
the FS pretty hard.    BBN might have had 4.1b, as I think that is where
Gurwitz & Walsh started the BBN2 code.   4.1c came pretty soon thereafter
as the 'beta' for 4.2 and that also went to IETF folks.   Joy left for Sun,
so I know Masscomp, Sun and DEC all had copies of 4.1c.   San wnj, Kirk and
Sam completed the beta, and got the formal release creating the BSD 4.2
release (which as Larry points out was the first truly networked UNIX) and
that went just anyone with a UCB license (and all hell broke loose because
- Henry Spencer's famous '*4.2 is just like Unix, only different*' quote).
 BBN released their alternative Network stack for sockets (*a.k.a.* BBN2 or
Bob Walsh version) and that fight started.  About a year or so later Kirk
and Sam got 4.3 out which was putting back in a number 4.1-ism so not so
much code broke, I think Van Jacobson's stuff up the hill at LBL went and
some of the new BBN stuff.  4.4 was at least a year after that.

ᐧ

On Sun, Jun 6, 2021 at 2:52 PM Richard Salz <rich.salz@gmail.com> wrote:

> Didn't 4.1c have some kind of networking?
>

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

  reply	other threads:[~2021-06-06 19:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-06 18:03 Paul Ruizendaal via TUHS
2021-06-06 18:23 ` Clem Cole
2021-06-06 18:30   ` Larry McVoy
2021-06-06 18:35     ` Clem Cole
2021-06-06 18:40       ` Warner Losh
2021-06-06 18:52         ` Richard Salz
2021-06-06 19:02           ` Clem Cole [this message]
2021-06-06 19:18             ` arnold
2021-06-06 19:35               ` Clem Cole
2021-06-06 19:45                 ` arnold
2021-06-06 20:46                   ` Clem Cole
2021-06-06 18:53       ` Clem Cole
2021-06-06 18:39     ` Warner Losh
2021-06-06 19:23       ` Clem Cole
2021-06-06 19:08   ` Paul Ruizendaal via TUHS
2021-06-07 19:24   ` Greg A. Woods

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=CAC20D2Nbxce2dcZAfQQpMzbJ-2g_wpK3BJbkx+Lhh4j4imaYYw@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=pnr@planet.nl \
    --cc=rich.salz@gmail.com \
    --cc=tuhs@minnie.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).