Bug 87727 - Please create a symlink to the initrd image
Summary: Please create a symlink to the initrd image
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 9
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-01 20:17 UTC by H. Peter Anvin
Modified: 2007-04-18 16:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2004-09-30 15:40:43 UTC

Attachments (Terms of Use)

Description H. Peter Anvin 2003-04-01 20:17:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030211

Description of problem:
The RedHat-generated boot loader installation is frequently not suitable.  The
reliance on "grubby" to generate boot loader configs from templates has been at
least for me extremely error-prone, often resulting in unusable configurations,
which is why I refuse to use it.

Not using this configuration system is complicated by two things, which should
be easy to fix:

a) When the RedHat kernel RPMs are installed, they create symlinks to every
component (vmlinuz, System.map, module-info) *except* config and initrd.img.  In
particular initrd.img, which is used by the boot loader, is a problem in this
sense.  Please create these remaining symlinks.

b) It would be even nicer if the kernel rpm would invoke /boot/Makefile as part
of its postinstall script, if such a script exists.  For all I know, it might
already be doing this...

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a custom boot loader config;
2. Upgrade kernel via RPM
3. Try to boot

Actual Results:  Boot failure due to missing initrd

Expected Results:  Proper boot

Additional info:

Comment 1 David Mark North 2003-12-09 17:52:44 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.

Comment 2 Bugzilla owner 2004-09-30 15:40:43 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

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.