Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am upgrading my RedHat 9 kernel from 2.4.20-6 to 2.4.20-24.9 (Intersect Alliance custom kernel for SNARE). If the base part of the kernel ("2.4.20") is the same, I shouldn't have any problems with software or hardware becoming incompatible should I? I'm just not sure what is entailed in the upgrade process.
Can I upgrade a 2.2.xx kernel to 2.4.20-24.9? Might I have compatibility issues then?
I'm not really sure what that means. I guess I may have asked the question wrong.
What I'm asking is, for any normal system, is there anything that you need to consider when patching the kernel (only changing the EXTRAVERSION).
The VERSION, PATCHLEVEL, and SUBLEVEL (a.k.a. "2.4.20") is the same - the only thing changing is the EXTRAVERSION ("-24.9snare") at the end of the kernel version, making it "2.4.20-24.9snare".
changiing the kernel extraversion won't make any different to kernel
only that when u run some
make modules_install
u will have modules install in different directory
this is usefull if u want to make a new kernel code and not overwrite the existing kernel
and do take care of proper configuration in the kernel
If the new kernel is a precompiled kernel provided in an RPM file you can easily install it alongside your previous kernel.
Since you are using RH9 I presume you are using grub as you bootloader and the new kernel RPM will add to your bootloder configuration without manual intervention. Both kernels will be available for booting, in case of an issue with the new kernel.
If you have kernel modules that need to be compiled against your kernel source, (such as nVIDIA display driver) you will have no X windows until you install the matching kernel sources and compile the driver against them.
Even if the VERSION, PATCHLEVEL, and SUBLEVEL (a.k.a. "2.4.20") is the same - the only thing changing is the EXTRAVERSION ("-24.9snare") at the end of the kernel version, making it "2.4.20-24.9snare", IF you have kernel modules that need to be compiled against your kernel source, you will need to recompile them in order to install them in the new running kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.