From: Chet Ramey <chet.ramey@case.edu>
To: Will Senn <will.senn@gmail.com>, 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:04:17 -0500 [thread overview]
Message-ID: <1e78ebf7-476c-9a3c-76b2-2eb0a5d17dd6@case.edu> (raw)
In-Reply-To: <ba3447f6-243e-ec69-bd2b-5523c3893eb3@gmail.com>
On 2/1/22 4:34 PM, 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?
He seems to be saying that everything post-VAX was where the project lost
its way.
My recollection is that the switch from VAX to Tahoe was mostly driven by
funding, hardware donations, and the Berkeley departments' and computing
center's desire to move to the VAX 8000 series, which IIRC the CSRG was not
prepared to support. (I'm a little fuzzy on the timing of that last piece.)
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
next prev parent reply other threads:[~2022-02-01 22:04 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 [this message]
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
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=1e78ebf7-476c-9a3c-76b2-2eb0a5d17dd6@case.edu \
--to=chet.ramey@case.edu \
--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).