The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] 2.11BSD pl 0 recovered (mostly) PRELIMINARY
Date: Wed, 3 Jun 2020 21:38:43 -0600	[thread overview]
Message-ID: <CANCZdfonmzQ+p=epaSLsccp6se6FRKy4gPmTnkmwa-itOeL78Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]

OK. I've written a script to take the 2.11BSD pl 195 tape and reverse apply
all the patches that we have to get back to 2.11BSD original.

There's some problems. The biggest one is that ld.c was rewritten during
this series and what it replaced is lost. And the 2.10.1 ld.c isn't what's
in 2.11BSD and the patches to get from 2.10.1 to 2.11 don't seem to be out
there. And the other patches in the series make it clear that patches are
missing. 2.11BSD likely will work with 2.10.1's ld, so this isn't fatal.

There's 122 other files that I recovered from 2.10.1. Almost all of those
are a good guess, if not what's actually in 2.11. Many of these can be
verified via other means. Some of these can be snagged from comp.bugs.2bsd
(that's how as was recovered).

There's a number of small cosmetic changes made via copying, some to get
rid of redundant files, etc. I think these don't matter for the function of
the system, but are small differences from the actual tape that shipped.

I still need to try to still create a tape and try to compile. And forward
apply all the patches and create a git repo from it.

All things considered 99% of the files have been recovered at this point.

It's early days, but I've pushed this to github for comments.

http://github.com/bsdimp/mk211bsd

It just assumes you have the Tuhs archive (including the new Usenet
section) and that apout works on your computer. It works on FreeBSD for
sure. No clue about anything else...

Warner

[-- Attachment #2: Type: text/html, Size: 1815 bytes --]

                 reply	other threads:[~2020-06-04  3:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CANCZdfonmzQ+p=epaSLsccp6se6FRKy4gPmTnkmwa-itOeL78Q@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --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).