You are not logged in.
Hello,
I am using kernel26-beyond (currently at 2.6.19), but every time a vanilla kernel gets upgraded, I get kernel-headers upgraded also (currently at 2.6.20). I wonder if wouldn't be better if there was different kernel-headers-beyond package for kernel26-beyond kernels? I am just afraid I could have problems while compiling some programs while vanilla and beyond variants of kernel are out of sync.
I imagine this is valid for other variants of kernels as well.
Another solution would be to release all the kernel variants at the same time, but I don;'t know if it would be possible.
Regards,
miko
Offline
kernel-headers should be in sync with what glibc has been compiled with (glibc actually has a not tight-enough dependency right now because I left the version at 2.6.19). Without recompiling glibc, it's not recommended to up- or downgrade the kernel-headers package. Running an older kernel should not cause any harm, many different distributions do it also. To make things clear: debian installs Debian Sarge with 2.6.8 kernelheaders, but ships by default with a 2.4 kernel.
Offline
Just to get this straight - only when glibc is compiled against new kernel-headers (e.g. 2.6.21) it is safe to upgrade kernel-headers (to 2.6.21) even if the used kernel version is still 2.6.19 ?
Offline
Just to get this straight - only when glibc is compiled against new kernel-headers (e.g. 2.6.21) it is safe to upgrade kernel-headers (to 2.6.21) even if the used kernel version is still 2.6.19 ?
yes, and glibc will be recompiled when the kernel headers are updated, so you're able to upgrade safely.
You can use any kernel you like (within reason), it doesnt have to match the kernel-headers version.
Offline
Thank you - your answer is appreciated.
Offline