From: Greg 'groggy' Lehey <grog@lemis.com>
To: Will Senn <will.senn@gmail.com>, Larry McVoy <lm@mcvoy.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] BSD 4.1, 4.1x, Quasijarus, and 4.3x
Date: Wed, 2 Feb 2022 11:38:36 +1100 [thread overview]
Message-ID: <20220202003836.GE17267@eureka.lemis.com> (raw)
In-Reply-To: <20220201214753.GA25875@mcvoy.com> <ba3447f6-243e-ec69-bd2b-5523c3893eb3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2215 bytes --]
On Tuesday, 1 February 2022 at 15:34:53 -0600, Will Senn wrote:
> All,
>
> I did my research on this, but it's still a bit fuzzy (why is it that
> people's memories from 40 years ago are so malleable?).
>
> 1. What are y'all's recollections regarding BSD 4.1's releases, vis a
> vis the VAX. In McKusick's piece, Twenty Years of Berkeley Unix, I get
> one perspective, and from Sokolov's Quasijarus project, I get quite
> another.
Kirk was there the whole time, from far earlier until the end of the
CSRG. Sokolov came later, and to my recollection he wasn't involved
in core BSD at all. I don't have any personal recollections of the
time, but it seems clear who is more plausible.
> 5. Has anyone unearthed an original 4.1 tape, or is Haertel's
> reconstruction of the 1981 tape 1 release as close as it gets?
Clearly this is beyond what is on the 4 CD set, right? That tree
contains a file TAPE with the comments (inter alia)
Extracted from two 4.1BSD distribution tapes dated 7/10/81.
First label on the tape:
4.1bsd VAX UNIX System 7/10/81
5 files on tape:
1 (boot stuff) 2 (root dump)
3 (/usr) 4 (/usr/src) 5(4.0/4.1)
last three are tar; 1600 bpi
But presumably you know that. Was this the Haertel reconstruction you
mention?
On Tuesday, 1 February 2022 at 13:47:53 -0800, Larry McVoy wrote:
> On Tue, Feb 01, 2022 at 03:34:53PM -0600, Will Senn wrote:
>> 2. Sokolov implies that the CSRG mission started going off the rails with
>> the 4.3/4.3BSD-Tahoe and it all went pear shaped with the 4.3-Reno release,
>> and that Quasijarus puts the mission back on track, is that so?
>
> I think the issue was that some of the core CSRG people went off to
> form BSDi to try and sell BSD on PCs.
BSDI came later, and the founders weren't CSRG people, though some
CSRG people did join the company. I think the real issue was that
CSRG no longer had a purpose: the research aspect was over and done
with, and the funding dried up.
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2022-02-02 0:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 21:34 Will Senn
2022-02-01 21:47 ` Larry McVoy
2022-02-01 22:04 ` Chet Ramey
2022-02-01 22:18 ` Dan Cross
2022-02-02 0:22 ` Clem Cole
2022-02-02 0:43 ` Brad Spencer
2022-02-02 1:19 ` Will Senn
2022-02-02 1:35 ` Will Senn
2022-02-05 23:57 ` Chris Hanson
2022-02-02 1:30 ` Will Senn
2022-02-01 23:40 ` George Michaelson
2022-02-01 23:54 ` Steve Nickolas
2022-02-02 0:38 ` Greg 'groggy' Lehey [this message]
2022-02-02 1:02 ` Seth Morabito
2022-02-02 10:28 ` Hans Rosenfeld
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=20220202003836.GE17267@eureka.lemis.com \
--to=grog@lemis.com \
--cc=lm@mcvoy.com \
--cc=tuhs@minnie.tuhs.org \
--cc=will.senn@gmail.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).