would have to comment on the reasons for the lack of a series 3 EL5 kernel.
Hmm, who's that making a racket?
There are three factors to consider when attempting to drop a new kernel source tarball into an Enterprise Linux environment:
(1) Are you able to correctly package the required end product?
(2) Will the userland utilities respect the new product?
(3) How "far away" from the official EL package is your new product?
The phrase "a kernel too far" was used by NedSlider
in respect of (3) and was quoted by toracat
in a blog posting
As Enterprise Linux 6 is now available, the general advice is that those persons who require features not supported by the EL 5 kernel (with, possibly, the addition of supplementary kmod
package(s)) should upgrade to the EL 6 product.
packages available from the ELRepo Project
should really be considered as "super kmod" packages and used for testing purposes only to identify features that could be backported to the distributed kernel package. The kernel-ml
packages were never conceived to be "drop-in" replacements for use with deployed systems. That said, I do use the earliest EL 5 kernel-ml series package with a vintage (in excess of 12 years of age) hardware system which is my desktop workstation (a Dell OptiPlex GX1
with a solitary Pentium III
processor, clocked at 450 MHz and with 768MB of RAM.)
It is perfectly possible to package a linux-3.x series tarball as a kernel-3.x.y series kernel package, without any renaming. The value that can be obtained by doing so appears to be minimal, to me. However, if asked, I would be willing (when time and the build system permits) to prepare an "unofficial" kernel-ml-3.x.y.el5.elrepo package set for selected persons to use as a "plaything".