Subject: Re: How many Vaxes?
To: None <jkunz@unixag-kl.fh-kl.de>
From: NetBSD Bob <nbsdbob@weedcon1.cropsci.ncsu.edu>
List: port-vax
Date: 02/22/2000 14:26:45
> > and don't forget a "limit datasize unlimited"
> Ohh yes. This was the reason why my first attempts to build current
> faild. And it may be necessary to build and install the librarys and
> gcc before a "make build".
OK.. This is why I was getting at the whys and wherefores. I did not
relish turning the machine on for weeklong compiles and not do one of
these little tidbits and have it crash.
So, that points to:
0. Unroll appropriate tarballs into /usr/src and /usr/xsrc.
Don't confuse the system and x top-level tarballs.
1. Make the kernel from current:
cd /usr/src/sys/arch/vax/conf
config GENERIC (configure the generic kernel)
cd ../compile/GENERIC
make depend ; make (depend and make current kernel)
cp netbsd /netbsd/14T (spare a current kernel in root)
cp /netbsd /netbsd.current (keep a previous copy just in case)
cp netbsd /netbsd (put a new current copy in root)
2. Make/install the libs from current:
(what?) (dummy, here needs input. Any gotchas?)
3. Make the gcc suite from current:
(what?) (dummy, here needs input. Any gotchas?)
4. Make the system from current: (This seems to be in the docs)
cd /usr/src (?)
make build (?)
(Are there specific make targets to be aware of other than make build?)
5. Make X if necessary?
(what? Will X run OK on my VS3100/M38 with the VSX-40(?) card?)
(That would be cool!)
Any other details that are NOT in the docs section that I need to be
aware of?
Any other details from the docs section or from the release builders
notes of such that I should be aware of for the current -current?
Since I am not in a cvs capable location, at home, and have to ferry
sources in on tape or cd, is there any reason to keep previous
build trees? I have been mv'ing src to S14R or something like that
as a spare and then unrolling a completely new tarball set to update
from the previous to current. Is that the best way to handle that?
Thanks
Bob