Bug 10299 - Custom kernels with modules lack .rhkmvtag
Summary: Custom kernels with modules lack .rhkmvtag
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-03-22 06:48 UTC by kenneth_porter
Modified: 2008-08-01 16:22 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2004-09-30 15:38:46 UTC


Attachments (Terms of Use)

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/



Note You need to log in before you can comment on or make changes to this bug.