RHEL3: Problem going from RH 2.4.20 to Linus 2.4.33

[David Douthitt]

I compiled a version of Linus' kernel 2.4.33 for CentOS 3 (RHEL 3) and
found that several programs started failing with core dumps or lockups.

It seems to center on two different things: the clone() call, and some
kind of file locking call that isn't supported ("fuserlock"?)

The clone() call resulted in core dumps; the other resulted in
programs receiving an unexpected "not implemented" result and entering
an endless loop waiting for a positive result.

Any tips? I'd like to keep the kernel current....

[Nils Breunese (Lemonbit)]

Post by David Douthitt
I compiled a version of Linus' kernel 2.4.33 for CentOS 3 (RHEL 3)
and found that several programs started failing with core dumps or
lockups.
It seems to center on two different things: the clone() call, and
some kind of file locking call that isn't supported ("fuserlock"?)
The clone() call resulted in core dumps; the other resulted in
programs receiving an unexpected "not implemented" result and
entering an endless loop waiting for a positive result.
Any tips? I'd like to keep the kernel current....

CentOS 3 is still maintained, so why not just use yum to get the
latest CentOS 3 kernel? Or do you specifically need features from the
latest 2.4 kernel version?

And most importantly: why are you posting this to the Fedora Legacy
list? CentOS has forums, mailinglists, etc.

Nils Breunese.

[Stephen John Smoogen]

Post by David Douthitt
I compiled a version of Linus' kernel 2.4.33 for CentOS 3 (RHEL 3) and
found that several programs started failing with core dumps or lockups.

You can not use 2.4.33 on Centos 3 or RHL 9 systems. The base kernel
for RHL-9 and RHEL-3/Centos-3 have several incompatible sections
backported from the 2.5.xx kernel series to give features that were
wanted but not in the 2.4 kernel. Thus you can not have the most
current 2.4.xx kernel. If you are wanting to do that you will be
wanting a different OS than any of the 'Enterprise' systems.

Post by David Douthitt
It seems to center on two different things: the clone() call, and some
kind of file locking call that isn't supported ("fuserlock"?)
The clone() call resulted in core dumps; the other resulted in
programs receiving an unexpected "not implemented" result and entering
an endless loop waiting for a positive result.
Any tips? I'd like to keep the kernel current....
--
fedora-legacy-list mailing list
https://www.redhat.com/mailman/listinfo/fedora-legacy-list