Description of problem: Existing depmod configuration files allow for one to override a specific set of Red Hat supplied kernel modules with external replacements using a depmod.conf file (one specific to the driver via /etc/depmod.d). But these files prior to RHEL5.3 can only override all or nothing - there is no ability to target a specific wildcard set of kernels. This was added to 5.3 and is required in 5.2 in order to correctly deliver targeted driver update RPMs.
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: * depmod configuration files allow end users to override a specific set of kernel modules with external replacements via /etc/depmod.d. However, module-init-tools did not correctly handle "override" statements in the depmod.conf file could only override modules for all installed versions of a kernel. Consequently, it was not possible to deliver driver update RPMs targeted to specific kernel versions. This updated package makes kernel version matching far more kernel-version specific and allows end-users to specify kernel module replacements for a specific set of installed kernels using wildcards in the configuration file.
Looks fine.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0056.html