-   Slackware (
-   -   Slackware 10.2 & 2.4.31 headers (

SlackwareInAZ 09-15-2005 07:05 PM

Slackware 10.2 & 2.4.31 headers
I know that this has been asked before, but I guess the subject is still a little confusing to me, so here goes:

Noticed that 10.2 still retains the 2.4.31 headers, along with the default kernel of 2.4.31. I know that you can optionally install the 2.6.13 kernel if you prefer. The second cd has 2.6.13 headers as well as alsa components.

I plan on using my own kernel that I am running now with 10.1 current. I always thought that the headers do not need to be changed, as these reflect the kernel used when Pat compiled glibc.

I prefer compiling my own kernel, with alsa as modules, Are the installed 2.4.31 headers fine with the 2.6 kernels, or do I need to match the headers to the kernel, and if not, why does Pat make the newer 2.6.x.x headers available along with the kernel.tgz and kernelsource.tgz?? Other than minor compiling work with kernels and some programs, I have no special needs that the 2.4.31 headers can't handle, but I wonder whether some small bit of system efficiency is being lost using these headers.

Shilo or any other knowledgeable Slacker??

Gary :confused:

MMYoung 09-15-2005 07:50 PM

While not in the same league as Shilo, my understanding is that unless you have some special need the kernel headers that are installed with Slackware should be fine. Matter of fact if you install the *other* kernel headers, and you build packages for "the public", it could cause problems.

You might want to take a look at the kernel-headers.WARNING text file in the same directory with the kernel packages and then decide.


Bruce Hill 09-17-2005 09:26 AM

You can use your kernel, and by all means don't mess with the original kernel headers. The header files should always match the library they're linked against. Pat's warning previously referred to should also be read with Linus Torvald's 5-year old warning.

All times are GMT -5. The time now is 07:07 PM.