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=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 27332 invoked from network); 8 Apr 2023 17:24:17 -0000 Received: from minnie.tuhs.org (2600:3c01:e000:146::1) by inbox.vuxu.org with ESMTPUTF8; 8 Apr 2023 17:24:17 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 1B92D432AD; Sun, 9 Apr 2023 03:24:13 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tuhs.org; s=dkim; t=1680974653; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-owner:list-unsubscribe: list-subscribe:list-post; bh=mmL16n8yaFXz/vQMZQZawr0/4SG0+mRxPSgS2qewWtw=; b=ocpKTqrg26H9Bk/WL+aed3iTr/x7+AdC+GU2czRh3TjHR80pkGJCYuY7L6mnRXDoWCf7sq 8FieRX1YXFIOr9Jl45clJCyXJ3B95oTx/qr6YlF7WxU3BX+cnzKSMvg4QVEFvd2fT65xV1 fUjeWFT0p3EbWNRdlYIKfg0w0guzhGM= Received: from vinci.rhwyd.co.uk (vinci.rhwyd.co.uk [IPv6:2a02:8012:22d7:0:1c19:f91c:97ae:89a7]) by minnie.tuhs.org (Postfix) with ESMTP id AA9C3432AC; Sun, 9 Apr 2023 03:24:00 +1000 (AEST) Received: by vinci.rhwyd.co.uk (Postfix, from userid 1001) id 74DDFA15; Sat, 8 Apr 2023 17:23:56 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 vinci.rhwyd.co.uk 74DDFA15 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aaronsplace.co.uk; s=mail; t=1680974636; bh=mmL16n8yaFXz/vQMZQZawr0/4SG0+mRxPSgS2qewWtw=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=s4w0myzu67j9qf84p9c+6wHre16SYmcnMmWIdf8wHPkcbTBclOCIe9nqG9yvDQwMT Sqjqj5Io3awCBD/rCamOZsI1tXhNjp4k/FL/xDf1H9/OLmzcEXSUqWEMwwgR5H+P0j rq5yO1u7/Q435CqjusyXlo3/gb3HWZzch7JgGdO4= References: <20200528214954.GA22861@minnie.tuhs.org> <877cumfgmu.fsf@carbon.rhwyd.co.uk> User-agent: mu4e 1.6.10; emacs 28.2 To: Warner Losh Date: Sat, 08 Apr 2023 18:22:35 +0100 In-reply-to: Message-ID: <87355afftd.fsf@carbon.rhwyd.co.uk> MIME-Version: 1.0 Content-Type: text/plain Message-ID-Hash: H62S33SWS2A3E4A277T4XLUPY5KP6G7M X-Message-ID-Hash: H62S33SWS2A3E4A277T4XLUPY5KP6G7M X-MailFrom: aaron@aaronsplace.co.uk 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: From: Aaron Jackson via TUHS Reply-To: Aaron Jackson > 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 cheers, Aaron