Easier way to Upgrade from 2.4.22 to 2.4.24?
 

Hi All,
I am considering using these 4 tgz to upgarde my cureent kernel 2.4.22 to 2.4.24. Can I just simply installpkg them and a reboot will turn my linux box in to 2.4.24? Or more work is required from me before it is a 2.4.24? I have not reached the level of doing a kernel compilation yet. :newbie:

http://www.slackware.com/pb/?vers=sl...-2.4.24-i486-1

http://www.slackware.com/pb/?vers=sl...-2.4.24-i486-1

http://www.slackware.com/pb/?vers=sl...-2.4.24-i386-1

http://www.slackware.com/pb/?vers=sl....4.24-noarch-1


Thanks!

You don't need the last two if you are not compiling programs. The kernel-headers are used when compiling 3rd party source code. The kernel-source is for compiling th kernel itself and includes its' own headers.
After installing the first two packages you'll need to edit /rtc/lilo.conf and add a section for your new kernel. Then run lilo -v -t (lilo in verbose, test mode) If no errors then run:
lilo to reinstall lilo.
To edit lilo.conf, just copy the section that points to your original kernel, changing the name tro the name of the new kernel, and give it a unique label.
Then, after running lilo and rebooting you can test your new kernel. If it doesn't work you can still reboot with your original kernel.

gnashley
thanks, I will try your steps out tonight when I am at home. Just one last thing to clarify, when LiLo is amended, the boot screen will then show these?:

Slack2.4.22 #My old kernel
Slack2.4.24 #new kernel
WinXP #Dual booting

And if my 2.4.24 doesn't work, i can just simply reboot and select 2.4.22?

Appreciate your help.:D

Correct.

ok, i did the the upgrade from 2.4.22 to 2.4.24, it went without any incident, booted fine. check using uname -r and it says 2.4.24. So i quickly jump to driver module making for my ltmodem, and it stopped at the error of mismtached kernel-headers. It says the machine have a 2.4.24 kernel with a 2.4.22 headers. I have removed 2.4.22 headers and installed 2.4.24 headers, but 2.4.22 is still being detected during the ./build_module. Any idea how I can get this solved? Will touch do the trick? Thanks!