Warren Toomey <wkt(a)tuhs.org> writes:
we have 2.11BSD patch 469 dated last month in the archive. Where
does it come from? Has anybody climbed the hill to import all the
patches into a git repo?
I know somebody tried a while back and reported here. They found it wasn't
possible to apply all the patches sequentially. I'd have to go look in
the mail archive for details.
Maybe it's time for someone else to have a go!
Stumbled upon this email thread while searching my inbox for some patch
info. I've managed to setup an automated pipeline for applying all
patches sequentially, producing a new disk image after each one. This
has been built as a GitHub workflow, and the images are then pushed up
to an S3 bucket for others to use.
At the very least, it is confirmation and verification that the released
patches can be applied sequentially, and each one leaves the system in a
bootable state, if applied correctly.
I've also been applying the patches to a fork of the source tree on
GitHub which Warner Losh created (maybe after this email thread). I've
been doing this in the patch-apply2023 branch but it's a bit of a mess
at the moment and doesn't build. The repo also includes an IBV11 card
driver which I wrote with the help of Toby Thain. I'm not sure whether
Steven would welcome patches for new features, rather than bug fixes,
but I'd be happy to generate a patch file if others wanted to control
their "modern" test gear from their PDP11.
At some point I'm planning to automate the process of generating the
installation tapes for each patch level. Not got round to this though,
yet - although it's Easter weekend, so I might have a play.
Any chance you could extend this to my work to
recreate the 2.11 as
released tapes? There are extra challenges in the first 200 patches,
including missing patches...
I'll take a look and see - that does sound like a mess to sort out