From: Warner Losh <imp@bsdimp.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: The Unix Heritage Society <tuhs@tuhs.org>
Subject: Re: [TUHS] a possible source for 4.1BSD tapes
Date: Sun, 10 Mar 2019 14:55:15 -0600 [thread overview]
Message-ID: <CANCZdfo4FF5FfkSrDoj-BAaEhqtmzLAWbpZb=HXx3_J4X62EnQ@mail.gmail.com> (raw)
In-Reply-To: <7wpnqzj7tr.fsf@junk.nocrew.org>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
On Sun, Mar 10, 2019 at 5:49 AM Lars Brinkhoff <lars@nocrew.org> wrote:
> Nigel Williams wrote:
> > Mike Haertel wrote:
> >> Also, while poking around the net, I've found a number of purported
> >> tape images of 4.1BSD dated 7/10/1981 that look to me to a little
> sketchy
> > http://bitsavers.trailing-edge.com/bits/UCB_CSRG/4.1_BSD_19810710.zip
>
> That's what I have been using for testing the MIT Chaosnet patches.
> If it's no good, I'd like to know.
>
There's also
http://bitsavers.trailing-edge.com/bits/BSD/BSD4.1_bootable.tap.gz which I
just noticed...
Warner
[-- Attachment #2: Type: text/html, Size: 1245 bytes --]
next prev parent reply other threads:[~2019-03-10 20:56 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 [this message]
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
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='CANCZdfo4FF5FfkSrDoj-BAaEhqtmzLAWbpZb=HXx3_J4X62EnQ@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=lars@nocrew.org \
--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).