From: Mike Haertel <tuhs@ducky.net>
To: The Unix Heritage Society <tuhs@tuhs.org>
Subject: Re: [TUHS] a possible source for 4.1BSD tapes
Date: Sun, 10 Mar 2019 18:15:18 -0700 [thread overview]
Message-ID: <201903110115.x2B1FI0V040212@ducky.net> (raw)
In-Reply-To: <de2eb3ea-a074-96bc-4910-91119f2c7e74@bitsavers.org>
Al Kossow writes:
> On 3/10/19 3:53 PM, Mike Haertel wrote:
> > Warner Losh writes:
> >> There's also
> >> http://bitsavers.trailing-edge.com/bits/BSD/BSD4.1_bootable.tap.gz which I
> >> just noticed...
>
> Likely a Memorex sticky tape that stripped its oxide when I tried to read it.
>
> These were read a long time before I had a tape oven.
>
> I've not dug back into what I still have from the 4BSD days, or in the CHM
> archives since I thought Kirk had this all covered.
I've double-checked, and disk1/4.1 from Kirk's archive is definitely 4.0,
(with the addition of a 4.0.upgrade directory taken from a 4.1 distribution).
As far as online 4.1 tape images are concerned, I did a bit more investigating:
AFAICT this file: http://bitsavers.org/bits/BSD/BSD4.1_bootable.tap.gz appears
to be the closest online thing to a 7/10/1981 version of 4.1.
This file: http://bitsavers.org/bits/UCB_CSRG/41bsd_7-10-81.tap contains files
with modification times up through June 1982.
Neither of these include the corresponding /usr/doc or /usr/ingres (which would
have been on the distribution tape #2). Those seem to be missing altogether.
next prev parent reply other threads:[~2019-03-11 1:15 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 [this message]
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
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=201903110115.x2B1FI0V040212@ducky.net \
--to=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).