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.
If I recompile my kernel, is there someway I can keep all my current modules, so that if something goes wrong I can successfully revert back to the old kernel, or do I not need to worry about this?
When recompiling a new kernel its always best to keep your existing server for these reasons, if the new one doesn't boot, you can use the old one to boot back into your system to diagnose the problem.
Rather than back up your modules, there is another way. Immediately after finishing your config, before doing 'make dep' (or 'make bzImage' if you are building 2.6), edit the Makefile in the toplevel of the linux source tree. There are lines that define VERSION, PATCHLEVEL, SUBLEVEL, and EXTRAVERSION. Set EXTRAVERSION to something you like, such as -b2 for build 2 (your second try.).
Then go ahead and build the kernel. For convenience, I name my kernels to match so:
cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.22-b2
You will find that the modules are installed in a directory called /lib/modules/2.5.22-b2, leaving your old modules untouched. When you run the new kernel, 'uname -r' will return '2.4.22-b2'. Now you also know how a kernel finds it's matching modules!
OK, I see.
So, if I build a 2.6 kernel, the modules created for it will be stored in a different location to where they currently are (wherever that is!!)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.