Bug 10299

Summary: Custom kernels with modules lack .rhkmvtag
Product: [Retired] Red Hat Linux Reporter: kenneth_porter
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-30 15:38:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description kenneth_porter 2000-03-22 06:48:05 UTC
When building and installing a new (experimental) kernel, "make
modules_install" fails to update .rhkvmtag in the target directory.
Furthermore, the modules overwrite those for the working kernel.

Desired behavior is to put the new modules in /lib/modules/VERSION-NAME,
where NAME is taken from /usr/src/linux/.name, and create a .rhkvmtag file
in this directory for /etc/rc.d/rc.sysinit to find. (What command does Red
Hat use to create this file? This is not documented! One that appears to
work is "strings vmlinux | grep `uname -n` > .rhkvmtag".)

Ideally one should be able to build a new kernel and revert to the old one
without manually changing links. It should be sufficient to set a name like
"test1" in the .name file and have that completely isolate the new kernel
from the old one.

Comment 1 Bugzilla owner 2004-09-30 15:38:46 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/