You are not logged in.
Hi,
I updated my system today and noticed that krenel-headers got updated to 2.6.32, although kernel is still 2.6.31.
Is that OK?
I mean, isn't that strange - to have headers of kernel 2.6.32 but older kernel actually running?
(I DO NOT have testing repo enabled, this is core repo)
Offline
That happened to me too today. How odd.
Offline
I've got new headers, too.
English is not my native language, sorry.
Offline
The version the kernel headers are has practically nothing to do with the actual kernel. I'm pretty sure that it is just for programs to include/link against or something similar. Having them be different versions is just fine.
Last edited by jac (2009-12-17 21:57:21)
Offline
Exactly... kernel-headers have everything to do with the toolchain (gcc, binutils, glibc, kernel-headers...) and not to do with the kernel. And it did go through [testing], just as all packages in [core] do.
Online
The headers are for building modules for the kernel, for example the nvidia module.
I believe the kernel-headers should match the library you link (glibc) not the kernel, so it shouldn't matter that they are newer than the kernel.
edit: oops Allan beat me to it... man 8 minutes to type this lol
Last edited by dyscoria (2009-12-17 22:21:01)
flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)
Offline
Allright I was just being curious... Thanks for info, didn't mean to complain or something...
Last edited by kralyk (2009-12-17 22:22:20)
Offline