plain 2.4.24 kernel / RedHat ES 3

[gboyce at badbelly.com (Gregory Boyce)]

It could be the Native Posix Thread Library (NPTL) patches.  I'm not
sure how a glibc compiled with NPTL deal with an unpatched kernel.  You
might be able to grab that patch itself from the kernel src.rpm file,
and just apply NPTL support from the enterprise kernel.

I'm not sure how cleanly it would apply though.

On Tue, 2004-01-20 at 23:56, Johannes Ullrich wrote:
> I ran into a very frustrating problem today. It all started out with
> trying to setup a grsecurity patched kernel on a RedHat ES 3 system....
> However, as it turns out, it wasn't grsecurity in this case that broke
> things.
> 
> Symptoms: 
> basic RedHat ES 3 install, dual CPU intel hardware.
> If you replace the kernel with an unpatched 2.4.24
> kernel, the system boots fine, but it looks like some programs (e.g.
> host, dig are two that pointed me to the problem) can no longer fork.
> They just segfault.
> 
> Has anybody found a way around this?
> 
> As mentioned in the intro, the goal of this is to setup a grsecurity
> patched kernel. I usually just patch a vanilla kernel, as the patch will
> not apply cleanly against the RedHat source tree (many, many .rej files,
> some of which are in code I don't want to touch)
> 
> I got RH 9 systems running with no problem, but they are all single CPU.
> 
> Workarounds?
> 
> 
>