The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dugo@xs4all.nl (Jacob Goense)
Subject: [TUHS] Pristine version of 2.11BSD
Date: Mon, 21 Dec 2015 23:30:48 +0100	[thread overview]
Message-ID: <6aed342543e03173571d464a65d9ccb3@xs4all.nl> (raw)
In-Reply-To: <20151221190502.GC67307@server.rulingia.com>

On 2015-12-21 20:05, Peter Jeremy wrote:
> On 2015-Dec-21 15:06:21 +0100, Jacob Goense <dugo at xs4all.nl> wrote:
>> On 2015-12-21 10:19, Tom Ivar Helbekkmo wrote:
>>> I just heard from Steven Schultz, who is surprised that we don't have
>>> the original 2.11 distribution in the archive.  Steven says:
>>> 
>>>> 	I was certain that a base 2.11 is in the TUHS archive.   There was 
>>>> a
>>>> 	tapeset sent down under and I recall someone working on a way to
>>>> 	simulate a tape drive over a serial line so 2.11 could be loaded.
>>> 
>>> Does this ring a bell, anyone?
>> 
>> From the PUPS mailing list archives:
>> From: wkt at dolphin.cs.adfa.oz.au (Warren Toomey)
>> Date: Tue, 21 Nov 1995 09:19:41 +1100 (EST)
> ...
>> I've also moved 2.11BSD into the ftp archive on henry.cs.adfa.oz.au.
> 
> There are several copies of 2.11BSD in the TUHS archives, the oldest 
> appears
> to be http://www.tuhs.org/Archive/PDP-11/Boot_Images/2.11_on_rl02/ but
> it's at patch level 303.

There was at least one older set in the archives.

http://minnie.tuhs.org/PUPS/archive_details.html mentions:

     2.11BSD
     -------

     This is a complete distribution of 2.11BSD up to patch level 277, 
sent in
     by Steven Schultz. The distribution includes the tape bootstrappers.

Patch 277 was from around Oct 28 1995, which closely matches Warren's 
post.

A late 1992 USENET post from Schultz regarding corrupt files in the
base 2.11BSD master tapes doesn't give me the idea they were real 
keepers.
Post at http://oldbsd.org/c.b.2bsd.10ccd2.txt



  reply	other threads:[~2015-12-21 22:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14  9:51 [TUHS] 2.11BSD mirror Warren Toomey
2015-12-14 10:30 ` Lars Brinkhoff
2015-12-14 11:01   ` Warren Toomey
2015-12-16  0:02     ` Jacob Goense
2015-12-16  0:19       ` Warren Toomey
2015-12-16  0:37         ` Jacob Goense
2015-12-16  4:37           ` arnold
2015-12-17 22:43       ` [TUHS] Pristine version of 2.11BSD Warren Toomey
2015-12-17 22:45         ` Warner Losh
2015-12-18  2:49           ` Random832
2015-12-18  0:34         ` Mary Ann Horton
2015-12-18 14:02           ` Jeremy C. Reed
2015-12-18 22:31             ` Warren Toomey
2015-12-18 11:04         ` Tom Ivar Helbekkmo
2015-12-19 14:16           ` Tom Ivar Helbekkmo
2015-12-19 22:44             ` Tom Ivar Helbekkmo
2015-12-19 23:55               ` Jacob Ritorto
2015-12-20  2:41                 ` Random832
2015-12-20 12:12                   ` Jacob Ritorto
2015-12-20 21:37               ` Jacob Goense
2015-12-21  9:19                 ` Tom Ivar Helbekkmo
2015-12-21 14:06                   ` Jacob Goense
2015-12-21 19:05                     ` Peter Jeremy
2015-12-21 22:30                       ` Jacob Goense [this message]
2015-12-22  0:44                         ` Warren Toomey
2015-12-22 21:12                     ` Dave Horsfall
2015-12-18 13:27         ` Tom Ivar Helbekkmo
2015-12-18 13:50           ` Tom Ivar Helbekkmo

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=6aed342543e03173571d464a65d9ccb3@xs4all.nl \
    --to=dugo@xs4all.nl \
    /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).