From: Aaron Jackson via TUHS <tuhs@tuhs.org>
To: Warren Toomey <wkt@tuhs.org>
Cc: tuhs@tuhs.org, tuhs@minnie.tuhs.org
Subject: [TUHS] Re: Latest 2.9BSD and 2.11BSD
Date: Sat, 08 Apr 2023 17:33:00 +0100 [thread overview]
Message-ID: <877cumfgmu.fsf@carbon.rhwyd.co.uk> (raw)
In-Reply-To: <20200528214954.GA22861@minnie.tuhs.org>
Warren Toomey <wkt@tuhs.org> writes:
>> I see 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!
>
> Cheers, Warren
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.
https://github.com/AaronJackson/2.11BSD-Action
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.
https://github.com/AaronJackson/2.11BSD
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.
Cheers,
Aaron
--
https://aaronsplace.co.uk
next prev parent reply other threads:[~2023-04-08 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 16:40 [TUHS] " Warner Losh
2020-05-28 21:49 ` Warren Toomey
2020-05-29 0:59 ` Warner Losh
2023-04-08 16:33 ` Aaron Jackson via TUHS [this message]
2023-04-08 17:09 ` [TUHS] " Warner Losh
2023-04-08 17:22 ` Aaron Jackson via TUHS
2023-04-08 17:26 ` Warner Losh
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=877cumfgmu.fsf@carbon.rhwyd.co.uk \
--to=tuhs@tuhs.org \
--cc=aaron@aaronsplace.co.uk \
--cc=tuhs@minnie.tuhs.org \
--cc=wkt@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).