On Tue, Mar 11, 2008 at 09:12:53PM -0700, Tracy R Reed wrote:
But that is just the kernel, no modules. A huge chunk of the kernel is the modules these days. If you slim it down to only the modules you need it can go a lot faster but I never bother because cpu time is cheap compared to my time. Hmm...I just tried to do a make modules and it complained that the current kernel doesn't have modules enabled. Since when does the Linus kernel ship without modules enabled? I guess what I've got here is a more or less complete kernel build in 1m32s.
The 2.6 kernels don't have a separate target for modules, it all gets built as one happy family. The default kernel configuration file starts from a file depending on your architecture, which definitely has modules enabled, so I'm not sure what exactly is going on there. If you want to be masochistic, you can always: 'make allyesconfig' before starting the compile. This should build everything that makes sense for your architecture. I'm running this now on my Core 2 Duo just to get an idea of the longest it could take to build a kernel. David -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
