Bug 87727
Summary: | Please create a symlink to the initrd image | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | H. Peter Anvin <hpa+redhat> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | hans, katzj, north |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:40:43 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
H. Peter Anvin
2003-04-01 20:17:17 UTC
I was just about to submit this same bug, but for perhaps a different reason. For those folks who already have grub installed (other systems running on the same machine) the logical approach is to boot into another system and make the missing symlink in the first place. Though that works fine, when an update happens and no subsequent symlink is make to the new initrd, booting fails. The fix is obvious so there's no disaster, but on the other hand it seems as if using this symlink in the first place would avoid much grief, particularly for those who don't know what's going on. This still applies to Fedora Core 1, where I intended to submit this bug. 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/ |