The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Seth Morabito" <web@loomcom.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] BSD 4.1, 4.1x, Quasijarus, and 4.3x
Date: Tue, 01 Feb 2022 17:02:05 -0800	[thread overview]
Message-ID: <47c39383-eca8-4ba4-9f39-731962588d18@www.fastmail.com> (raw)
In-Reply-To: <ba3447f6-243e-ec69-bd2b-5523c3893eb3@gmail.com>

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

On Tue, Feb 1, 2022, at 1:34 PM, 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. In terms of popularity and in terms of stable performance, what say you? Was 4.1 that much better than 4BSD? Was 4.1as obsolete immediately as McKusick says? 4.1b sounds good with FFS, was it? 4.1c's the last pre 4.2 release, but it sounds like it was nearly a beta version of 4.2... 
> 
> 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? 

My recollection from 1997 or 1998 is that Sokolov appeared out of nowhere, alone, with (as someone else in this thread best put it) a "revolutionary zeal", and decided to create Quasijarus with the specific goal of supporting VAXen beyond the models that had been originally supported under 4.2. Sokolov was 18 or 19 at the time, so I can certainly understand the revolutionary zeal (I miss mine!). Beyond that, I don't think anything else ever came out of it.

-Seth
--
  Seth Morabito
  Poulsbo, WA
  web@loomcom.com


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

  parent reply	other threads:[~2022-02-02  1:11 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
2022-02-02  1:02 ` Seth Morabito [this message]
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=47c39383-eca8-4ba4-9f39-731962588d18@www.fastmail.com \
    --to=web@loomcom.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).