Robert Bonomi wrote:
> I've got to be missing something.
>
> I'm building a custom kernel, for the first time on a new 6.2 install. with
> _everything_ I want/need specified via 'option' and/or 'device' lines in the
> config file (along with appropriate 'hints' in the hints),
>
> 'make buildkernel KERNCONF={mumble}' has been running for *more*than*six*hours*
> on a Pentium 1 200mhz machine -- and is compiling all sorts of stuff tat
> I'm _not_using_ in the custom kernel.

It is building kernel modules which you can kldload into working kernel. You can choose what to build with MODULES_OVERRIDE variable or disable building modules at all with NO_MODULES.

Have a look at /usr/share/examples/etc/make.conf

> I've discovered the 'NO_KERNELCLEAN' flag so it won't start over from
> scratch -every- time you build a kernel, but this is bloody ridiculous.
> The _entire_ point of the 'make' facility is to avoid recompiling anything
> that doesn't _need_ to be re-compiled. Yet the distributed makefile, _by_
> _default_ starts off by deleting *EVERY*LAST*OBJECT*FILE*!!!

I guess the point of cleaning first is that unexperienced user could compile kernel after modifying sources (to get new release for example). That way build process won't break unexpectedly. As you wrote, define NO_KERNELCLEAN (or NO_CLEAN in general) if you want it that way.

HTH,

-- Karol Kwiatkowski