From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 27664 invoked from network); 8 Apr 2023 17:26:41 -0000 Received: from minnie.tuhs.org (2600:3c01:e000:146::1) by inbox.vuxu.org with ESMTPUTF8; 8 Apr 2023 17:26:41 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 0172B432B2; Sun, 9 Apr 2023 03:26:37 +1000 (AEST) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) by minnie.tuhs.org (Postfix) with ESMTPS id 0E8F4432B2 for ; Sun, 9 Apr 2023 03:26:29 +1000 (AEST) Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-9476e2fa157so227754066b.3 for ; Sat, 08 Apr 2023 10:26:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; t=1680974787; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5O1ULk65yvb6trFusgjh6Y5/obbA4DEEoldz5u5hUTk=; b=zsXmaqljKn2lORIZJ42yYx1k5UYTvIT35nQnjMJarr/IsaATwsMdAgKafqmZC5xUNF 95w1JEmCDjdVYVr+NCI4OElySTMyUFa4xh3sbqVbLH0rMVawIK9DvdhuKM/mTNd8L7V7 pdkzGhKUOh9vIZre/+hNAz/L59uZM3lWvBOsct/cKdLL9bsqH9yX1nolqbBbgTEZ0xrR GWQhSw97sRG07Hj/Enk8HIH14gYrQe4LEoDaeCJvST3ygslZJ3UFj/b/gU4mIpsgfPC3 E9WXb+FvuNDxMGOHTf+nD8SF5KwSOKv2Vdl7PNNNwO/RkQFTFblreYaLinem64Wd/mDc zchw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680974787; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=5O1ULk65yvb6trFusgjh6Y5/obbA4DEEoldz5u5hUTk=; b=SE7bcqk2aFoab5IEPz/IVNFFHg1sXlie00jPOLz/L2TmSUdflh5bdjXdPWA967eIh1 K56Y188CrH3xW1NEKjBdHxccbDlBuJiP7kSmVMKph2Sg5EbAogvFAxtwSJrVU4aLElfl V/M9xOoNRK5xOvOrtYG3it3UWucBIrvzZGBe/p/r+rH9pX5xMBZJlPcFkEDVz7fcLSnh lIMzK38ByusalNRMPg2+HXKhQ1GHH/WnuNtfjG4xTri+RKETtSODPuxZ7ILAEe32cK9K lNiKQAAnIfx/ZHZOew2mz2a0ywX44Kzqu8g/J7SnLeylXFcF/1JTX5OvprCiKRsIu/6N /t1A== X-Gm-Message-State: AAQBX9dCM0QJYfISSoJWL2rRt4f3BYkeuvx4jJYokLv/cbOSPnI0PnjA Ufxi9KKqJ71B4htS7EVO9RoOZoYChjAOc4osbgMniA== X-Google-Smtp-Source: AKy350abLe7oO46voCKwoC0BlxnMv3A7AStPBTW20YwwnYXDjeowD+Hv1HM+zwOeGa2yqWLez/BVRfgQ9HQLgMVUmiU= X-Received: by 2002:a50:cd84:0:b0:4ad:6052:ee90 with SMTP id p4-20020a50cd84000000b004ad6052ee90mr3146143edi.7.1680974787310; Sat, 08 Apr 2023 10:26:27 -0700 (PDT) MIME-Version: 1.0 References: <20200528214954.GA22861@minnie.tuhs.org> <877cumfgmu.fsf@carbon.rhwyd.co.uk> <87355afftd.fsf@carbon.rhwyd.co.uk> In-Reply-To: <87355afftd.fsf@carbon.rhwyd.co.uk> From: Warner Losh Date: Sat, 8 Apr 2023 11:26:16 -0600 Message-ID: To: Aaron Jackson Content-Type: multipart/alternative; boundary="000000000000130c4005f8d6714c" Message-ID-Hash: NFXGAFR43UQQVGGGT56R54FMFVK7CGKK X-Message-ID-Hash: NFXGAFR43UQQVGGGT56R54FMFVK7CGKK X-MailFrom: wlosh@bsdimp.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Warren Toomey , The Eunuchs Hysterical Society , TUHS main list X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Latest 2.9BSD and 2.11BSD List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000130c4005f8d6714c Content-Type: text/plain; charset="UTF-8" On Sat, Apr 8, 2023, 11:23 AM Aaron Jackson wrote: > > Warren Toomey 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. > > Warner Losh writes: > > > 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... > > > > Warner > > If you are talking about this: > https://github.com/bsdimp/mk211bsd > > I'll take a look and see - that does sound like a mess to sort out > though :D > Yes. It's why I've not done it yet. Going backwards was hard enough :) I'd love to help, but don't have the time to drive it. Warner > cheers, > Aaron > > --000000000000130c4005f8d6714c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Apr 8, 2023, 11:23 AM Aaron Jackson <aaron@aaronsplace.co.uk> wrote:=
>=C2=A0 Warren Toomey <wkt@tuhs.or= g> writes:
>
>=C2=A0 >>=C2=A0 =C2=A0 I see we have 2.11BSD patch 469 dated last= month in the archive. Where
>=C2=A0 >>=C2=A0 =C2=A0 does it come from? Has anybody climbed the= hill to import all the
>=C2=A0 >>=C2=A0 =C2=A0 patches into a git repo?
>=C2=A0 >
>=C2=A0 > I know somebody tried a while back and reported here. They = found it wasn't
>=C2=A0 > possible to apply all the patches sequentially. I'd hav= e to go look in
>=C2=A0 > the mail archive for details.
>=C2=A0 >
>=C2=A0 > Maybe it's time for someone else to have a go!
>=C2=A0 >
>=C2=A0 > Cheers, Warren
>
>=C2=A0 Stumbled upon this email thread while searching my inbox for som= e patch
>=C2=A0 info. I've managed to setup an automated pipeline for applyi= ng all
>=C2=A0 patches sequentially, producing a new disk image after each one.= This
>=C2=A0 has been built as a GitHub workflow, and the images are then pus= hed up
>=C2=A0 to an S3 bucket for others to use.
>
>=C2=A0 https://github.com/AaronJackso= n/2.11BSD-Action
>
>=C2=A0 At the very least, it is confirmation and verification that the = released
>=C2=A0 patches can be applied sequentially, and each one leaves the sys= tem in a
>=C2=A0 bootable state, if applied correctly.
>
>=C2=A0 I've also been applying the patches to a fork of the source = tree on
>=C2=A0 GitHub which Warner Losh created (maybe after this email thread)= . I've
>=C2=A0 been doing this in the patch-apply2023 branch but it's a bit= of a mess
>=C2=A0 at the moment and doesn't build. The repo also includes an I= BV11 card
>=C2=A0 driver which I wrote with the help of Toby Thain. I'm not su= re whether
>=C2=A0 Steven would welcome patches for new features, rather than bug f= ixes,
>=C2=A0 but I'd be happy to generate a patch file if others wanted t= o control
>=C2=A0 their "modern" test gear from their PDP11.
>
>=C2=A0 https://github.com/AaronJackson/2.11BSD=
>
>=C2=A0 At some point I'm planning to automate the process of genera= ting the
>=C2=A0 installation tapes for each patch level. Not got round to this t= hough,
>=C2=A0 yet - although it's Easter weekend, so I might have a play.<= br>
Warner Losh <imp@bsdimp.com> writes:

> 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...
>
> Warner

If you are talking about this:
https://github.com/bsdimp/mk211bsd

I'll take a look and see - that does sound like a mess to sort out
though :D


Yes. It's why I've not done i= t yet. Going backwards was hard enough :) I'd love to help, but don'= ;t have the time to drive it.

Warner
cheers,
Aaron

--000000000000130c4005f8d6714c--