From: arnold@skeeve.com
To: tuhs@ducky.net, lm@mcvoy.com
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] a possible source for 4.1BSD tapes
Date: Tue, 12 Mar 2019 06:44:09 -0600 [thread overview]
Message-ID: <201903121244.x2CCi99p020772@freefriends.org> (raw)
In-Reply-To: <20190311173845.GU31834@mcvoy.com>
Larry McVoy <lm@mcvoy.com> wrote:
> Other than for history's sake, I don't see the value of 4.1, it wasn't
> a great release (even though Masscomp did their changes to 4.1c if I
> remember correctly. Clem?). 4.2 was the first release that I remember
> being pretty solid and 4.3 improved on that.
I'm with Clem; we ran 4.1 at Georgia Tech and it was pretty solid.
The big changes in 4.2 were the fast file system, the networking, and
how signals worked.
The fast file system used more space on the disk for its metadata;
people who had nearly full disks on 4.1 didn't have enough room to
restore their filesystems with the change to 4.2!
Later on I ran two vaxen at the Emory U computing center with 4.2; they
were heavily (over)loaded. When 4.3 came out it had a huge amount of fixes
and performance tuning; when we switched to 4.3 + NFS from Mt. Xinu we
saw a big drop in the load. To this day I am convinced that the move to
4.3 kept us from having to buy more hardware.
Arnold
next prev parent reply other threads:[~2019-03-12 12:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 7:31 Mike Haertel
2019-03-09 23:24 ` Nigel Williams
2019-03-10 11:18 ` Lars Brinkhoff
2019-03-10 20:55 ` Warner Losh
2019-03-10 22:53 ` Mike Haertel
2019-03-11 0:25 ` Al Kossow
2019-03-11 1:15 ` Mike Haertel
2019-03-11 5:46 ` Jason Stevens
2019-03-11 17:28 ` Mike Haertel
2019-03-11 17:38 ` Larry McVoy
2019-03-11 18:33 ` Lars Brinkhoff
2019-03-11 18:41 ` Clem Cole
2019-03-12 6:21 ` Nigel Williams
2019-03-12 6:32 ` Jason Stevens
2019-03-12 12:44 ` arnold [this message]
2019-03-11 21:47 ` Al Kossow
2019-03-23 17:50 ` reed
2019-03-24 4:19 ` Lars Brinkhoff
2019-03-10 8:20 ` arnold
2019-03-10 15:50 ` Mike Haertel
2019-03-10 19:54 ` arnold
2019-03-10 20:33 ` Warner Losh
2019-03-25 17:19 Richard Tobin
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=201903121244.x2CCi99p020772@freefriends.org \
--to=arnold@skeeve.com \
--cc=lm@mcvoy.com \
--cc=tuhs@ducky.net \
--cc=tuhs@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).