The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] BSD 4.1, 4.1x, Quasijarus, and 4.3x
Date: Tue, 1 Feb 2022 17:18:29 -0500	[thread overview]
Message-ID: <CAEoi9W5YdSqxygueWP2Cr=WxNpU6Bzwvj7FDkJv_VAGk9Od2ow@mail.gmail.com> (raw)
In-Reply-To: <ba3447f6-243e-ec69-bd2b-5523c3893eb3@gmail.com>

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

On Tue, Feb 1, 2022 at 4:35 PM Will Senn <will.senn@gmail.com> 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?
>

Bluntly, no. Sokolov fell deeply into the nostalgia trap, and combined it
with a revolutionary zeal that was off-putting at best. As far as I know,
it was never more than one individual's project, and boasts of reclaiming
the mantle of CSRG and BSD are grossly exaggerated. The world changed, and
Unix moved in a different direction to accommodate; there's really no going
back.

3. I've gotten BSD 4.2 and BSD 4.3 releases built from tape and working
> very well. I just can't decide whether to go back to one of the 4.x
> releases (hence question 1), or go get Quasijarus0c - thoughts on why one
> might be more interesting than another?
>

Quasijarus is like 4.3 with some bug fixes and enhancements. If you want to
run something like 4.3 in an emulator, it's not bad; I'm running it for a
ham radio project (just for fun) and it's Y2K compliant and seems reliable.

4. Is Quasijarus0c end of the line for VAX 4.xBSD? Why does tuhs only have
> Quasijarus0 and 0a, was there something wrong with 0b and 0c?
>

Well, no. Both OpenBSD and NetBSD ported back to the VAX, but the OpenBSD
effort has ended due to lack of hardware and interest. It appears that
NetBSD is still being actively developed on the VAX, however, so it's
possible to get a "modern" 4.4BSD derived system on that architecture.

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?
>

For the fifth time today this reminded me that I wanted to find my images
from Kirk's CD collection and move them over to another machine. Sigh.

        - Dan C.

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

  parent reply	other threads:[~2022-02-01 22:19 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 [this message]
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
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='CAEoi9W5YdSqxygueWP2Cr=WxNpU6Bzwvj7FDkJv_VAGk9Od2ow@mail.gmail.com' \
    --to=crossd@gmail.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).