| | List |
| Subject: | Re: kernel building question |
| Poster: | bonomi@host122.r-bonomi.com(RobertBonomi) |
| Date: | Wed, 21 Mar 2007 23:04:25 -0000 |
| Related Postings: | 1 2 3 4 5 6 |
In article ,
Karol Kwiatkowski wrote:
>Hi Robert, all,
>
>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,
*BIG* help. NO_MODULES is where I want to start. I _want_ a monolithic
kernel, *without* loadable module capability. One less security vulnerability
to worry about that way.
The full kernel build just finished. 9 hours 58 minutes, 47 seconds.
I'd hate to think what would have happened if I'd missed a config line
that some other option/device depended on. And it blew up at the very
end of things. Add one line to the config, and wait -another- 10 hours
to find out if that fixed things, or not. :(((
One thing's for sure. I'm -not- going to try a 'buildworld' on this
dinosaur. Well, maybe at closing time, the day I leave on vacation
for at least a week.
|
|