From: Henry Bent <henry.r.bent@gmail.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] 4.3BSD-Tahoe Restoration
Date: Mon, 4 Oct 2021 13:51:20 -0400 [thread overview]
Message-ID: <CAEdTPBebgWTf+RwApSd0Oc71SPp14m54J5Qijk=RDHY-PMW4Hw@mail.gmail.com> (raw)
In-Reply-To: <4fbe7200-a619-9523-4edc-612b5dd73bcc@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On Mon, 4 Oct 2021 at 13:42, Will Senn <will.senn@gmail.com> wrote:
> On 10/4/21 12:22 PM, Henry Bent wrote:
> > 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).
>
> Hi Henry,
>
> I expect folks who actually ran this can weigh in with the 'real world'
> perspective. What I can offer is that the document entitled, "Installing
> and Operating 4.3BSD-tahoe UNIX* on the VAX" by the folks doing the
> release (CSRG) is probably canonical:
>
> http://blog.livedoor.jp/suzanhud/BSD/4.3BSD_Tahoe_VAX.pdf
>
>
Well now I feel a little silly. I did look in the source tree for a
document like this but couldn't find one. It does appear, however, in the
installed (for Tahoe) tree in /usr/doc/smm/01.setup.
-Henry
[-- Attachment #2: Type: text/html, Size: 1994 bytes --]
next prev parent reply other threads:[~2021-10-04 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 17:22 Henry Bent
2021-10-04 17:41 ` Will Senn
2021-10-04 17:51 ` Henry Bent [this message]
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='CAEdTPBebgWTf+RwApSd0Oc71SPp14m54J5Qijk=RDHY-PMW4Hw@mail.gmail.com' \
--to=henry.r.bent@gmail.com \
--cc=tuhs@minnie.tuhs.org \
--cc=will.senn@gmail.com \
/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).