Re: Kernel legacy

2009-02-01 Thread Ben Hutchings
On Sun, 2009-02-01 at 23:31 +0100, Klaus Ethgen wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Am So den 1. Feb 2009 um 18:57 schrieb Luk Claes: > > > With lenny the provided glibc seems to be incompatible to kernel 2.4. > > > There are many systems out there still running with ke

Re: Kernel legacy

2009-02-01 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am So den 1. Feb 2009 um 18:57 schrieb Luk Claes: > > With lenny the provided glibc seems to be incompatible to kernel 2.4. > > There are many systems out there still running with kernel 2.4 cause > > stability. (My servers which needs to be stable

Re: Kernel legacy

2009-02-01 Thread Bastian Blank
On Sun, Feb 01, 2009 at 05:26:30PM +0100, Klaus Ethgen wrote: > With lenny the provided glibc seems to be incompatible to kernel 2.4. The Linux 2.4 support ended with the Etch release. Even for Etch it is only supported for upgrades. > Is there any scenario what happens to such systems when lenny

Re: Kernel legacy

2009-02-01 Thread Luk Claes
Klaus Ethgen wrote: > Just to bring that back to discussion: > > With lenny the provided glibc seems to be incompatible to kernel 2.4. > There are many systems out there still running with kernel 2.4 cause > stability. (My servers which needs to be stable all run Kernel 2.4.) s/lenny/etch/ > Is

Re: Kernel legacy

2009-02-01 Thread Russ Allbery
Klaus Ethgen writes: > Background: The glibc in lenny is compiled to be incompatible with > kernels lower than 2.6. I do not know if there are options to use newer > glibc with older kernels. There is other software in lenny that isn't built to be compatible with older kernels as well. For exam

Kernel legacy

2009-02-01 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just to bring that back to discussion: With lenny the provided glibc seems to be incompatible to kernel 2.4. There are many systems out there still running with kernel 2.4 cause stability. (My servers which needs to be stable all run Kernel 2.4.) I