GENERIC won't config?

On Sat, Jan 21, 2006 at 01:38:38PM -0500, James K. Lowden
wrote:
> Quentin Garnier wrote:
> > Use a config(1) program that match the kernel
sources.  That question
> > has been asked so many times now...
> > 
> > Please use build.sh when you don't know very
precisely what you are
> > doing.
> 
> I see.  I didn't realize config(8) was mated to the
sources or would
> change in a way that wasn't backwards compatible.  I
thought it was more
> like a compiler.  I also didn't know pkgsrc would
update it.  Thank you
> for the information.  
> 
> FWIW, I followed the kernel documentation:
> 
> 	http://www.netbsd.org/Documentation/kernel/#how
_to_build_a_kernel
> 
> which told me to ftp the kernel sources and specifies
config(8).  It
> doesn't mention build.sh and doesn't provide it.   IIRC
that's what I did.
>  I didn't expect pkgsrc to change things from under me.
 I expected the
> pkgsrc toolchain not to disturb my base system, apart
from adding things
> to /var and /etc.  

build.sh is not needed if sources mathc your kernel.  This
is NOT the case
here, you're trying to build either -current or a 3.0 tree
otherwise you
wouldn't have references to pf.

build.sh is documented in the "traking -current"
chapter.  What is said
there applies starting with 2.0.

-- 
Quentin Garnier - cubecubidou.net - cubeNetBSD.org
"When I find the controls, I'll go where I like, I'll
know where I want
to be, but maybe for now I'll stay right here on a silent
sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.