From: Henry Bent <henry.r.bent@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] 4.3BSD-Tahoe Restoration
Date: Mon, 4 Oct 2021 13:22:37 -0400 [thread overview]
Message-ID: <CAEdTPBf19-iFQPFgh3zNdJz86qaLxR4BfeG2A8_sNwnA=BKzKg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1406 bytes --]
next reply other threads:[~2021-10-04 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 17:22 Henry Bent [this message]
2021-10-04 17:41 ` Will Senn
2021-10-04 17:51 ` Henry Bent
2021-10-04 19:22 ` David Barto
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='CAEdTPBf19-iFQPFgh3zNdJz86qaLxR4BfeG2A8_sNwnA=BKzKg@mail.gmail.com' \
--to=henry.r.bent@gmail.com \
--cc=tuhs@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).