[elrepo] Announcement: EL5 Updated kernel-ml Release [Version 2.6.37-4.el5.elrepo]

[Alan Bartlett]

Announcing the release of updated kernel-ml-2.6.37-4.el5.elrepo
packages into the EL5 elrepo-kernel repository:

http://elrepo.org/tiki/kernel-ml

A configuration change (CONFIG_VETH=m) has been applied in this
routine update as a result of the following RFE:

http://elrepo.org/bugs/view.php?id=119

The following packages are currently syncing to the mirrors:

x86
kernel-ml-2.6.37-4.el5.elrepo.i686.rpm
kernel-ml-devel-2.6.37-4.el5.elrepo.i686.rpm
kernel-ml-headers-2.6.37-4.el5.elrepo.i386.rpm
kernel-ml-PAE-2.6.37-4.el5.elrepo.i686.rpm
kernel-ml-PAE-devel-2.6.37-4.el5.elrepo.i686.rpm

x86_64
kernel-ml-2.6.37-4.el5.elrepo.x86_64.rpm
kernel-ml-devel-2.6.37-4.el5.elrepo.x86_64.rpm
kernel-ml-headers-2.6.37-4.el5.elrepo.x86_64.rpm

noarch
kernel-ml-doc-2.6.37-4.el5.elrepo.noarch.rpm

src
kernel-ml-2.6.37-4.el5.elrepo.src.rpm

We provide these kernels for hardware testing in an effort to identify
new/updated drivers which can then be targeted for backporting as kmod
packages. Meanwhile, these kernels may provide interim relief to
people with non-functional hardware. We stress that we consider such
kernels as a last resort for those who are unable to get their
hardware working using the RHEL-5 kernel with supplementary kmod
packages.

These packages are provided As-Is with no implied warranty or support.
Using the kernel-ml may expose your system to security, performance
and/or data corruption issues. Since timely updates may not be
available from the ELRepo Project, the end user has the ultimate
responsibility for deciding whether to continue using the kernel-ml
packages in regular service.

The packages are intentionally named kernel-ml so as not to conflict
with the RHEL-5 kernels and, as such, they may be installed and
updated alongside the regular kernel. The kernel configuration is
based upon a default RHEL-5 configuration with added functionality
enabled as appropriate.

If a bug is found when using these kernels, the end user is encouraged
to report it upstream to the Linux Kernel Bug Tracker [1] and, for our
reference, to the ELRepo bug tracker [2]. By taking such action, the
reporter will be assisting the kernel developers, Red Hat and the Open
Source Community as a whole.

Thank you,

The ELRepo Team.

[1] http://bugzilla.kernel.org/
[2] http://elrepo.org/bugs/