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_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31744 invoked from network); 4 Oct 2021 17:23:30 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 4 Oct 2021 17:23:30 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 17E949CBD4; Tue, 5 Oct 2021 03:23:26 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id A6AAE9CB0F; Tue, 5 Oct 2021 03:22:51 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="J6y7fR7c"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id CD89E9CAF1; Tue, 5 Oct 2021 03:22:47 +1000 (AEST) Received: from mail-pf1-f182.google.com (mail-pf1-f182.google.com [209.85.210.182]) by minnie.tuhs.org (Postfix) with ESMTPS id 69D909CAE9 for ; Tue, 5 Oct 2021 03:22:47 +1000 (AEST) Received: by mail-pf1-f182.google.com with SMTP id p1so9055462pfh.8 for ; Mon, 04 Oct 2021 10:22:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=e0Z17e8FDG7kOp66XIME8X1e7bpyWqqu8QX3EJD7cgY=; b=J6y7fR7cGFINBE7e+/30Kpfpy4NaHBEi5DNbAE55IG5u5OqHqIHljKCqOegq8BFbR5 +k189N78N/ak2ZRuo5Ku2m+Hxug2BkVSiM+JAw1323CVWXWHIUEVhr3PRiGNrVzrMscd EAZidO1dYJZXoB7F/QdG6oAIjjiafHhCqAZ9IIWhCCA3jpFh1My9CUg11XUkHKeT/eY4 qVWqV7/dJxoMn+y11TZA1pS4cysvXYGHl6I6Pu/vFWOGTaz2V4m5aq3v9de5s4a9iH82 6o+tYkvtLIZHwTX1PsjplN9QAfVFjzr++42BhzWWcCxhfhJxa/ntz0PSArZUK4gZK8mO SeBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=e0Z17e8FDG7kOp66XIME8X1e7bpyWqqu8QX3EJD7cgY=; b=lOB9q2+t5zaSTcJuuB8ofAt63I1kB9YYCfNhSMJUckGlkwg7F43tNejzGg6Wq1iV/M /PstsMpo+eFnl29Bk9SfiKYYndSXmGtNzXdYTIs74OMWSO9otYpOvkY/C/dJemEpgW+4 Xcm0YblUQe40YJyZRK/3tIh81h6DwJTDIFSOshoEYhljI0n0Sl6Me3Ah2pq/slLFaujL 9frokKptA1WK248SHHTZVSRfVnzgvNEuRfYmedGNikxbt/Twfw72XallWlBUyIw63krf /JBY0BcqJJiHqsSM2+BgdwA4mD+U1BgSNBEjeYsLlt+sQDrQDsywQCYWyDaNABgNA5ow 4Rvg== X-Gm-Message-State: AOAM5329XRZh7KY2hT8rLONgP7VkMYFpC3PDe/M8jJq0cRaPgBNGbrzw 421Bm7ncOIzgw52vuhwzKpWaTtu+9EckuX/kp7F7j/oS X-Google-Smtp-Source: ABdhPJwhFka1enGIWPbC/aB3t+EkBBmmcF+tqZ6YJOmunvvbmRTWaET40SoDJekk6YJdE5O52/MmKxU6LHbzJOwjzDc= X-Received: by 2002:aa7:9d0b:0:b0:44c:62a6:8679 with SMTP id k11-20020aa79d0b000000b0044c62a68679mr5855264pfp.0.1633368166657; Mon, 04 Oct 2021 10:22:46 -0700 (PDT) MIME-Version: 1.0 From: Henry Bent Date: Mon, 4 Oct 2021 13:22:37 -0400 Message-ID: To: The Eunuchs Hysterical Society Content-Type: multipart/alternative; boundary="0000000000005c70d705cd8a2905" Subject: [TUHS] 4.3BSD-Tahoe Restoration X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --0000000000005c70d705cd8a2905 Content-Type: text/plain; charset="UTF-8" Hello All, I am attempting to restore 4.3BSD-Tahoe to a usable state on the VAX. It appears, based on the work that I have done already, that this is possible. Starting with stock 4.3BSD I got a source tree into /usr/tahoe and using it I replaced all of /usr/include and /sys, recompiled and replaced /bin, /lib, and /etc, recompiled a GENERIC kernel, and from there I was able to successfully reboot using the new kernel. As far as I can tell (fingers crossed!) the hardest part is over and I'm in the process of working on /usr. My question is: how was this sort of thing done in the real world? If I was a site running stock 4.3BSD, would I have received (or been able to request) updated tapes at regular intervals? The replacement process that I have been using is fairly labor intensive and on a real VAX would have been very time intensive too. Fortunately two to three years' worth of changes were not so drastic that I ever found myself in a position where the existing tools were not able to compile pieces of Tahoe that I needed to proceed, but I could easily imagine finding myself in such a place. (This was, by the way, what I ran into when attempting to upgrade from 2.9BSD to 2.10BSD, despite a fully documented contemporary upgrade procedure). -Henry --0000000000005c70d705cd8a2905 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello All,

I am attempting t= o restore 4.3BSD-Tahoe to a usable state on the VAX.=C2=A0 It appears, base= d on the work that I have done already, that this is possible.=C2=A0 Starti= ng with stock 4.3BSD I got a source tree into /usr/tahoe and using it I rep= laced all of /usr/include and /sys, recompiled and replaced /bin, /lib, and= /etc, recompiled a GENERIC kernel, and from there I was able to successful= ly reboot using the new kernel.=C2=A0 As far as I can tell (fingers crossed= !) the hardest part is over and I'm in the process of working on /usr.<= /div>

My question is: how was this sort of thing done in= the real world?=C2=A0 If I was a site running stock 4.3BSD, would I have r= eceived (or been able to request) updated tapes at regular intervals?=C2=A0= The replacement process that I have been using is fairly labor intensive a= nd on a real VAX would have been very time intensive too.=C2=A0 Fortunately= two to three years' worth of changes were not so drastic that I ever f= ound myself in a position where the existing tools were not able to compile= pieces of Tahoe that I needed to proceed, but I could easily imagine findi= ng myself in such a place.=C2=A0 (This was, by the way, what I ran into whe= n attempting to upgrade from 2.9BSD to 2.10BSD, despite a fully documented = contemporary upgrade procedure).

-Henry
--0000000000005c70d705cd8a2905--