Bug 159696
| Summary: | kernel rebuild revision naming | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Curtis Doty <curtis> |
| Component: | kernel | Assignee: | Dave Jones <davej> |
| Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | CC: | herrold, pfrields, wtogami |
| 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: | 2005-08-30 01:48:29 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I'm puzzled as to what this buys you, given this is purely a cosmetic thing, and isn't used by anything. The advantage is for typsically overworked sysads who have to occasionally rebuid a kernel to identify a bug or test a feature not enabled by Red Hat. This simple change makes it easier to track what one's done after the fact. For example, I have a cluster of a few dozen mostly identical hosts who are manifesting a bizarre bug (I think) and I need to test. So I cook up another kernel on one host, I get the EXACT SAME FILENAME on a different build on a different host. (Of course, we Red Hat devotees out here in the real world don't have the luxury of a fancy schmancy beehive buildsystem.) So what I propose, would be a more unique naming scheme for user initiated kernel rebuilds. I.e. kernel-2.6.11-1.27_FC3.jake.rpm kernel-2.6.11-1.27_FC3.bill.rpm Are clearly *different* builds. An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. committed to cvs in all trees. And after this change uname -r reports 2.6.12-1.1447_FC4.vvs, while all file and directory names has vvs@vvs suffix, so modprobe doesn't find modules :-( |
Please consider the following patch or something similar that will provide better granularity for those of us rebuild srpms on various systems who do not have access to the beehive cluster. --- kernel-2.6.spec 2005-05-17 16:50:40.000000000 -0700 +++ kernel-2.6gk.spec 2005-05-30 18:58:15.000000000 -0700 @@ -21,7 +21,7 @@ %define sublevel 11 %define kversion 2.6.%{sublevel} %define rpmversion 2.6.%{sublevel} -%define rhbsys %([ -r /etc/beehive-root -o -n "%{?__beehive_build}" ] && echo || echo .`whoami`) +%define rhbsys %([ -r /etc/beehive-root -o -n "%{?__beehive_build}" ] && echo || echo .`whoami`@`hostname -s`) %if %{FC3} %define release %(R="$Revision: 1.27 $"; RR="${R##: }"; echo ${RR%%?})_FC3%{rhbsys} %endif