kernel install question =)

[gcb]

okay. i just configured and compiled my third kernel...the first two didn't work, but i'm hoping this one will...i'm ready to issue the <code>make modules
make modules_install</code>
commands, which i didn't use with the first two kernels (& i'm assuming that's why they didn't work), & i have a question about it...
my default kernel that installed with the distro (mandrake8), has the modules that it has installed in /lib/modules/<kernel_release>
right? so if i issue the above commands, it will copy over the files in this directory, rendering my default kernel useless, right? so what if this new kernel i just compiled doesn't work? i've trashed my original files, and that plain stinks...what do i need to do to make sure that i don't mess things up? cool. thanks. :D

[Dark Ninja]

Actually, when you run 'make modules' ...etc... I was pretty sure that a different directory is created (in the name of the kernel version you are compiling.) But, just in case, just back up your existing modules.


Dark Ninja

[Malakin]

If you do a "make modules_install" on the *same* kernel it will overwrite the modules.

A smooth way of getting around this is edit your "/usr/src/linux/include/linux/version.h" file and add onto the the version info. I made mine "2.4.8-26mdk-malakin" so when I recompiled the kernel that came with mandrake 8.1 and did a "make modules_install" it put the modules into "/lib/modules/2.4.8-26mdk-malakin" instead.

[bigrigdriver]

Easier solution. After you do the configuration, and before you do "make", edit the makefile. About 3 or 4 lines down, you should see a line EXTRAVERSION=. Put something after the equal sign, such as a version number or an abbreviation relating to some special feature of the kernel you wanted (that's why you recompiled, no?). When you run make, make modules, make modules_install, you will get a new /lib/modules directory: the original will not be affected.