Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
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 do not know debian, but the subject seems not to be distro-dependent.
The change from 2.2.x to 2.4.x kernel is not so easy. At least glibc relies on kernel header files - they should be the ones which glibc was compiled against.
So just running 2.4.x kernel witout recompiling the other packages will crash the system.
For solving your problem the better way is to configure and recompile (the latest version) of the 2.2.x kernel.
If in doubt, do apt-cache show package.
Where package is the name of the kernel you want more info about.
When you found one do f.ex.:
apt-get install kernel-image-2.4.18-bf2.4
These kernels use initrd, to implement them. The install will modify your lilo.conf to include the new kernel, and it will keep the old under Linux.old, so if something went wrong you can always boot the Linux.old to boot from the old kernel
BTW, I would recommend against apt-getting the kernel-image, but instead downloading it from www.kernel.org
Only problem I can think of is that you will most likely want to install and configure the iptables. ipchains is available for compatibility, but I'd recommend just making some new iptable rules.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.