Bug 211339
Summary: | typo in some of the kernel packages that add kernel name labels in new stanzas | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Joshua Giles <jgiles> |
Component: | mkinitrd | Assignee: | Peter Jones <pjones> |
Status: | CLOSED WONTFIX | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.8 | CC: | pjones |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | s390 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 18:40:32 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: |
Description
Joshua Giles
2006-10-18 18:51:00 UTC
This would most likely be a bug in /sbin/zipl, part of the s390utils package. Reassigning appropriately. (If this problem also occurs on ppc64, then an additional BZ should be entered.) Ernie, I just tried the 2.4.21-37.0.1.EL on s390 and the same problem occurs...so this could very well be a boot loader limitation. It also occurs on ppc64... Not sure why it gets cut off. I'm not sure if there are any length limitations for sections in zipl.conf, but afaik not. I'll double check with our IBM liasion next time he's here. Read ya, Phil OK, found the source of the problem: It's actually in grubby (part of mkinitrd) that ofc actually writes zipl.conf. There the title length is limited to 15 btes for lilo, yaboot, silo and zipl conf types. If i remember correctly this was actually really necessary for the RHEL3 kernels for those architectures, but i might confuse something here. Reassigning the bug though to the proper component. Read ya, Phil This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |