Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Sep 1999 16:37:44 +0200
From:      Brad Knowles <blk@skynet.be>
To:        Mike Tancsa <mike@sentex.net>, freebsd-stable@FreeBSD.ORG
Subject:   Re: Building new kernel fails?
Message-ID:  <v0420550cb402b8154e10@[195.238.1.121]>
In-Reply-To: <3.0.5.32.19990913100217.01bbb3e0@staff.sentex.ca>
References:  <3.0.5.32.19990913100217.01bbb3e0@staff.sentex.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
At 10:02 AM -0400 1999/9/13, Mike Tancsa wrote:

> Are you sure you want
> *default tag=.

	For ports and doc, I believe that this is correct.  At least, 
that's the way I interpret the comments in 
/usr/src/share/examples/cvsup/stable-supfile, as well as 
/usr/src/share/examples/cvsup/ports-supfile and 
/usr/src/share/examples/cvsup/doc-supfile.

	If this is not correct, I'd appreciate whatever advice you may be 
able to give.

> src-all
>
> Is all you really need.

	This doesn't get the crypto stuff, does it?  IIRC, it also 
doesn't get the ports or doc stuff.  Should these other things not be 
updated at the same time as /usr/src?

> Also, you will need to monitor and merge the changes in /etc.
>
> You dont mention anything about that.

	Uh, no.  I wasn't aware that this was necessary.  I take it I 
should do some searches on this "mergemaster" program I've seen 
referenced?

> Its probably safer if you do a
> config -r HOST to remove the old cruft in your compile directory, or
> rm -R ../../compile/HOST
> config HOST
> cd ../../compile/HOST
> make depend;make

	I got this same advice from another person on the list, and so 
far it appears that this has solved the problem.

	Out of curiosity, is it a good habit to get into to always do a 
"config -r HOST"?, or is this an unusual sort of thing that you might 
only want to do after having built a new machine and you now want to 
go rebuild the kernel so that it corresponds?

> I would suggest not doing autobuilds until you are more comfortable with
> the whole process.

	It was my understanding that "make buildworld" actually did the 
builds in a separate directory tree (something like 
/usr/obj/usr/src/tmp), and so long as you didn't do a "make 
installworld" on a machine where the previous "make buildworld" did 
not complete successfully, you should be okay.  Is this not an 
accurate statement?


	Since this is a rather lengthy process on this machine, if I can 
avoid the additional time of having to wait for "make buildworld" to 
complete, I'd like to do that.

	In this case, I did check the output of the results that had been 
mailed to me regarding the cvsup commands and the "make buildworld", 
and confirmed that things appeared to have been successful before I 
manually proceeded with a "make installworld".


	Is there something else I've missed?  I really would like to 
learn the proper way to do all this stuff, so any advice you may have 
would be appreciated, especially if you can help me understand the 
reasoning behind the advice.


	Thanks again!

-- 
   These are my opinions -- not to be taken as official Skynet policy
  ____________________________________________________________________
|o| Brad Knowles, <blk@skynet.be>            Belgacom Skynet NV/SA |o|
|o| Systems Architect, News & FTP Admin      Rue Col. Bourg, 124   |o|
|o| Phone/Fax: +32-2-706.11.11/12.49         B-1140 Brussels       |o|
|o| http://www.skynet.be                     Belgium               |o|
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
  Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.
   Unix is very user-friendly.  It's just picky who its friends are.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v0420550cb402b8154e10>