Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!ncar!tank!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.bugs.4bsd
Subject: Re: Installing 4.3-Tahoe on a VAX
Keywords: tahoe vax
Message-ID: <13484@mimsy.UUCP>
Date: 10 Sep 88 17:31:54 GMT
References: <4790@saturn.ucsc.edu>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 31

The first thing to do is fix /usr/include/machine; the second
thing to do is to build a new version of make(1)!  I suspect the
third thing to do is to recompile PCC, for which you need the
recompiled make.  The timezone code can wait until you have the
compiler compiling itself.  (I installed 4.3BSD-tahoe in many
small steps so some of this is guesswork.  Indeed, I have yet to
install much of the new /usr/src.)

I suggest NOT trying the kernel until you have at least /etc and /bin
built (in /nbsd or wherever you are rooting the new tree).  You will
want to run fsck to convert your file systems from old-style tables to
new, and you will probably want to label your disks (hp, ra disks only,
unless kre did the up driver); for this you will need the new /etc.
Also, the old fsck will complain about a bad superblock after running
the new kernel.  (I think I managed to get this into the installation
document.)

There may be small problems with a few of the VAX Makefiles, either
with not having had `make depend' run on them, or with ()s changed
to {} (I spotted one such in adb).  Note that the distributed
`mkdep' program must be able to rewrite the Makefiles.  mkdep and
/bin/make have been modified to put the dependencies in `.depend',
to avoid this, but that is probably not on the distribution tape
(I have a `beta' tape so what do I know? :-) ).

Once you have the compilers going, rebuild the C library, then rebuild
/usr/src, fixing Makefiles as needed (i.e., rarely).  Then a `make
install' should put everything into your new-binaries tree.  If you
have not already done so, by now you are ready to try a new kernel....
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris