On Wed, Oct 26, 2011 at 11:38 AM, Bryan J Smith <b.j.sm...@ieee.org> wrote:
> But also today, in the Enterprise Linux era, I typically still install the > "GA" Update kernel (e.g., 2.6.18-x for EL5, 2.6.18-x for EL6), and then > update afterwards with the errata kernel (e.g., 2.6.18-x.y.z and > 2.6.32-x.y.z). I can think of many reasons for this. > > But one, big reason is for kmods that may not directly resolve and/or load on > an errata kernel. Having the original, "GA" kernel works well one when one > has 3rd party kmods, and automation (e.g., weak-modules from > module-init-tools) loads them on errata kernels. kABI compatible kmods > should load without symbol issues, especially under the same update. I can only speak for ELRepo kmods. In principle, ELRepo's kmod packages are built against the oldest possible version of the kernel (with regard to the kABI compatibility). This means it is often the GA kernel. However, you do not need to have that kernel installed on the system. If the target kernel is not on the system, kmod installation process will create an appropriate directory (/lib/modules/<target-kernel-version>/extra/) and install itself in there. Likewise, removal/uninstallation of the kernel for which a kmod was installed is not a problem. Its extra/ directory will not be deleted. Akemi _______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
