On Sat, 25 Nov 2000 00:49, Mark Weaver wrote: > > But isn't the whole reason for compiling a new kernel so that you can > "reconfigure" the kernel more to your liking and needs rather than having > the new kernel configured exactly as the one you're currently running? Why > even bother if you're going to have it look the same. It will be doing > exactly the same thing. It is, but you've got to consider your starting point. 2 Possibilities :) Doing it with the kernel source from the distribution The kernel-source RPM only contains the default config that normally ships with vanilla kernels, so you grab the config file for the mandrake Kernel you happen to be currently running from the srpm package, copy it into the appropriate spot...and make changes....you don't have to try to figure out and emulate every line of Mandrake Kernel config, and you know that everything else your working with is going to work - its a lot easier (and less stressful) to just delete or add the bits your changing in make config than it is to go through every option (though I keep forgetting to change the subversion in the makefile). Using a new source Say 2.2.18 comes out and you don't feel like waiting for the RPM to be distributed. One of the great things about make oldconfig is if the configuration file dosn't match the source tree (due to new stuff being added or patches being removed) it updates the kernel config to match the new tree For example...a vanilla 2.2.18 source won't have reiser support, but almost all of Mandrakes configs do (the Mandrake kernel source has the reiser patch applied)..make oldconfig will zap the reiser section of the config file - needless to see, this can cause trouble if your really going over the top with what your using - as a check I usually keep a copy of the original config and then do a diff check between that and the config after make oldconfig. AG
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
