On Fri, 20 Aug 1999, Daniel R. Killoran,Ph.D. wrote:

> Ok, ok, not so fast... I have, in fact, installed all the {}.tar.gz stuff
> (although I am installing 1.4, not current), and I have built & installed
> the kernel. But when you say

OK

> >> What am I doing wrong? Is there some sort of cannonical order in which this
> >> stuff should be installed?
> >
> >Take a look at
> ><http://www.netbsd.org/Documentation/current/index.html>.
> >
> I will go fetch it in a minute, but I am not installing current.

Please do that. As I said, change "current" to "release", and it's all
good advice.
 
> >Now 'sed -e "/current/release/"' and you'll have an even better chance
> >of success.
> 
> Again, from what directory?

The "top" is /usr/src. Executive summary: Boot from the new kernel and
'cd /usr/src; make build > mklog 2>&1 & nice tail -f mklog', then
shutdown and reboot again after it's done.

If you're going from 1.4 -> {1.4,1.4.1,release} it should be that
simple. If you're coming from 1.3.x, you have to do it at least
*twice*. You'll probably need to rebuild parts of the tool-chain to
even get it to build once all the way through (I think only "flex",
"yacc", and "make"), and then you'd still only have a functionally
equivalent system. To have the (nearly?) identical thing as the binary
release, you'd need to build the world with the new compiler, ergo,
"make build" twice, then configure and build the kernel again.

You can build selected parts from almost anywhere in the tree except
the "dist" directories. E.g.: 'cd /usr/src/gnu; make includes && make
depend && make && make install', 'cd /usr/src/usr.bin/yacc; make
depend && make && make install'. But again, to get the same 1.4 that
everyone else calls 1.4, "make build" once or twice.