You wouldn't have "make cloneconfig" But you could keep copies of your .config file in /usr/src/linux -tosi Þann föstudagur 14 september 2001 20:30 skrifaðir þú:
Slightly off topic - if you have a Vanilla kernel, what files, or what could we cut and paste out of a file, that would enable us to keep a record of our current kernel config.
Brian Marr
On Saturday 15 September 2001 05:39, you wrote:
Þann föstudagur 14 september 2001 19:45 skrifaðir þú:
On Friday 14 September 2001 15:13 pm, Lourens Steenkamp wrote:
On Fri, 14 Sep 2001 13:47:46 -0400 Hello Bruce from Lourens:
[snip] " > On Friday 14 September 2001 19.14, Bruce Marshall wrote: " > > In my view, you should go straight to kernel.org and get their " files and " > > do the kernel from scratch. Much better-er. " > " 1) You get all the pieces. This is about the 5th response I've " given to " people who can't make things work with the SuSE pieces. (headers " missing, " etc) " " 2) You can compile it with your own choice of options. " " 3) Learn by doing. [end snip]
A question while this is being discussed - this vanilla vs SuSe thing has been bothering me (does'nt take much ...)
- I installed kernel-source-2.4.7.SuSE-15.i386.rpm. - make cloneconfig (to see what options had been previously installed) - make xconfig, loaded the .config from the above and changed it to suit myself - blah, blah
How would the end result from the above differ from the vanilla install?
Thanks for your time Bruce.
Bye.
If you load and configure from source, I suppose there is no difference.... It's the pre-compiled kernel's that are the problem I think.
I have gathered this from others who were unable to install VMware on the higher kernels when pieces of it were missing.
Way wrong ! There is a LOT that differs.
SuSE have done their own configuring ( and patching ) of the kernel. ( This was more true with 2.2.x than with 2.4.x but it's still true ).
The "vanilla" source is just that - vanilla.
If you are using any of the extended options in SuSE, you may well break them by using the vanilla sources.
And.. to run VmWare, the ONLY change that has to be done is to enable CONFIG_MODVERSIONS=y
Thus: ( if kernel-source-2.4.4.SuSE-17 ( or later ) is installed )
.config make dep make bzImage cp ./arch/i386/boot/bzImage /boot/vmlinuz
cd /usr/src/linux make cloneconfig mv .config .config.old sed 's/CONFIG_MODVERSIONS=n/CONFIG_MODVERSIONS=y/' < .config.old lilo shutdown -r now
Should suffice, if and ONLY *IF*, you have installed the *SAME* kernel-sources as you have a binary running kernel !!
( otherwise make cloneconfig may give improper output for the new kernel )
-tosi