linux header

[Gerardo Di iorio-2]

Why the version of linux-header is different from linux kernel package (linux26) ?

--
http://www.gerardodiiorio.com

-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

[René Rebe]

Gerardo Di Iorio wrote:
> Why the version of linux-header is different from linux kernel package
> (linux26) ?

Due several reason, major ones are:

    - headers are often randomly edited causing regressions in many packages
    - they define the stable ABI for applications and thus only have to be
      updated if new major features make it into the Linux kernel
 

--
  René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
  http://exactcode.de | http://t2-project.org | http://rene.rebe.name



-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

[Mike N]

Gerardo Di iorio-2 wrote:

Why the version of linux-header is different from linux kernel package
(linux26) ?

I have also wondered this, but this is not T2 specific weirdness. I have seen the same case in numerous other distros also. It has something to do with Kernel internal structures and application level ABI interface of kernel parts. For example see this web link: http://kerneltrap.org/node/6536

I don't know why T2 has different linux header package than the actual supported kernel, but I have always assumed it has something to do with how glibc and libc libraries are compiled in T2 (I have understood that some people prefer to have kernel headers matching the version used to compile libc or glibc package, not necessarly the same as kernel itself).

Other people just overwrite kernel headers package with the headers from self-compiled kernel package. I'm part of this group because I use couple of applications which expects to find latest Kernel enum and define entries.

I'd like to know what is the "correct" way to solve the difference between "stock kernel headers" and "latest self-compiled kernel" headers?

[René Rebe]

Hi,

Mike N wrote:

>
>
> Gerardo Di iorio-2 wrote:
>  
>> Why the version of linux-header is different from linux kernel package
>> (linux26) ?
>>
>>    
>
> I have also wondered this, but this is not T2 specific weirdness. I have
> seen the same case in numerous other distros also. It has something to do
> with Kernel internal structures and application level ABI interface of
> kernel parts. For example see this web link: http://kerneltrap.org/node/6536
>
> I don't know why T2 has different linux header package than the actual
> supported kernel, but I have always assumed it has something to do with how
> glibc and libc libraries are compiled in T2 (I have understood that some
> people prefer to have kernel headers matching the version used to compile
> libc or glibc package, not necessarly the same as kernel itself).
>
> Other people just overwrite kernel headers package with the headers from
> self-compiled kernel package. I'm part of this group because I use couple of
> applications which expects to find latest Kernel enum and define entries.
>
> I'd like to know what is the "correct" way to solve the difference between
> "stock kernel headers" and "latest self-compiled kernel" headers?
>
>  

If we would update the linux-header package with every kernel release
we would have random breakage where half (or sometimes nearly none)
of the packages would build.

Instead we (as other distributions) only update it when new features
make the trouble worth it.

René

--
  René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
  http://exactcode.de | http://t2-project.org | http://rene.rebe.name



-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2