From: Warner Losh <imp@bsdimp.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] 211BSD Version in the Unix Archive
Date: Mon, 20 Jul 2020 11:49:00 -0600 [thread overview]
Message-ID: <CANCZdfrd=e+jiNDy++0USd6HZ6V_xrY=CYr=Uyr3dA7sC+vfZg@mail.gmail.com> (raw)
In-Reply-To: <327c5b98-c48f-7855-0503-9c0f503af09c@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2063 bytes --]
On Mon, Jul 20, 2020 at 10:46 AM Will Senn <will.senn@gmail.com> wrote:
> Hi All,
>
> I'm currently doing some work with 211BSD and the best version that I've
> come across for my investigations is the one put together by Andre Luvisi,
> based on the distro in the Unix Archive at
> https://tuhs.v6shell.org/UnixArchiveMirror/Distributions/UCB/2.11BSD
>
You should look at the canonical tuhs archive at
https://www.tuhs.org/Archive/Distributions/UCB/2.11BSD/
> So far as I can figure out (and I'm a little bit fuzzy around the edges),
> this appears to be patch level 431, at least according to
> https://tuhs.v6shell.org/UnixArchiveMirror/Distributions/UCB/2.11BSD/VERSION.
> I have a number of questions that hopefully, someone can shed some light on:
>
1. Is it really pl 431?
>
Yes. It is.
> 2. How can I tell?
>
VERSION is always updated, so it is. If you are in doubt, you can look at
the patch files that's at
https://www.tuhs.org/Archive/Distributions/UCB/2.11BSD/Patches/ and they
all update VERSION.
> 3. Is it the latest tape image available (I've seen plenty of disk images,
> but those are already installed)?
>
Yes. Well, almost.
https://www.tuhs.org/Archive/Distributions/UCB/2.11BSD_patch457/ has a tape
that's updated to 457, lacking only the last 12 changes. A most current
tape hasn't been regenerated, at least in the archives. A quick search of
github shows there's a few PiDP-11 oriented versions but I've not looked
closely at them.
> 4. Is there a howto bring it up to the next patch level document lying
> around somewhere?
>
There's two or three efforts to create shell scripts to apply the patches.
I've not looked closely at them all yet...
> I've seen Warner's work on going the other direction and that's
> fascinating in it's own right, but I'd like to see about patching up to
> latest
>
When my work is done, there will be a github repo that has all the changes
applied, one at a time which can be used to generate context diffs or
something else that can be pushed to the PDP-11s that can be updated.
Warner
[-- Attachment #2: Type: text/html, Size: 4474 bytes --]
next prev parent reply other threads:[~2020-07-20 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 16:45 Will Senn
2020-07-20 17:49 ` Warner Losh [this message]
2020-07-20 18:03 ` Will Senn
2020-07-20 17:06 Will Senn
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='CANCZdfrd=e+jiNDy++0USd6HZ6V_xrY=CYr=Uyr3dA7sC+vfZg@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=tuhs@minnie.tuhs.org \
--cc=will.senn@gmail.com \
/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).