Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] [TUHS] Unix and SW Releases (was V7 et al from Will)
Date: Fri, 7 Aug 2020 17:07:52 -0400	[thread overview]
Message-ID: <CAC20D2NVMj3s5-f3TO2bb4zMz7MjtRVcCmd0tyydNEaBoG94-w@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfoUBAQhnqmnq2pKHGaUfa5+GNrM8BvsFkrRSx2bAUQ=9A@mail.gmail.com>

On Fri, Aug 7, 2020 at 4:23 PM Warner Losh <imp at bsdimp.com> wrote:

> 2.8BSD was supposed to be the last PDP-11 release: A final wrapup of
> everything, according to the release notes.
>
Yeah, that sounds right.  Bostic had moved into CSRG and I think he was
hacking on it less and less.  Also Ultrix/PDP-11 was out by then and Fred
Cantor had sort of displaced Keith as the PDP-11/UNIX wizard.



> However, there were a lot of PDP-11s in specialized niches that weren't
> easily replaced by more modern hardware, so 2.9, 2.10 and 2.11 happened as
> well.
>
You tell me from looking at the sources, do you know if there was any back
population to these releases from DEC?  The Ultrix team (aps et al) had fed
CRSG drivers and some stuff for the Vax.  Fred had a goal (took some pride)
in trying to make the PDP-11/Ultrix release very much plug and play, but I
had personally lost interest in the PDP-11 by then so I was not watching it
directly, only socially knowing many of the players.




> The formality of the release seemed to diminish a bit at each step (though
> that may just be my perceptions).
>
Well, the formality of anything before that was happenstance.  Because CSRG
was getting more formal, I think Keith and company were trying to
parrot the same schemes.  As I said, 4.1 and before like, Research was sort
of the state of the world when Joy made the tape.

To be fair, disk space was expensive.  So keeping a big hunk of space
dedicated to the 'release bits' was not really reasonable much less
imaginable.  It was only with CRSG that for the Vax there was 'enough'
hardware to have test machines and dedicated distribution.



> By the time we arrive at 2.11BSD, the tapes were produced by USENIX where
> you had to send proof of license to get the tape... These releases were
> driven by Seismo, and the USGS and/or military deployments from everything
> I've read...
>
That sounds right.   By the time of later 2.X versions UCB folks were much
less involved and I think you might be that USENIX took over some
distribution work (I was not on the board then, Steve might have been).

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200807/00c928c8/attachment.htm>


  reply	other threads:[~2020-08-07 21:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 20:20 clemc
2020-08-06 23:15 ` imp
2020-08-07  3:41   ` wobblygong
2020-08-07 14:27     ` cowan
2020-08-07 20:17       ` imp
2020-08-07 15:37     ` clemc
2020-08-07 20:23       ` imp
2020-08-07 21:07         ` clemc [this message]
2020-08-07  2:49 ` cowan
2020-08-07  2:56   ` usotsuki

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=CAC20D2NVMj3s5-f3TO2bb4zMz7MjtRVcCmd0tyydNEaBoG94-w@mail.gmail.com \
    --to=coff@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).