Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 233265 - mkinitrd doesn't link to
Summary: mkinitrd doesn't link to
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: David Lawrence
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-21 12:50 UTC by Steven Rostedt
Modified: 2008-05-06 19:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 19:23:33 UTC

Attachments (Terms of Use)

Description Steven Rostedt 2007-03-21 12:50:16 UTC
Description of problem:
When building my own kernel (from either or from Fedora source) and
installing it, the system would panic on boot saying "Failed to execute /init".

Looking into this (placing debug into the kernel to see what's wrong). I found
that it was returning -ENOENT (file not found) on /lib/  Looking
into the contents of the initrd, sure enough, it didn't have a /lib/

I looked at my working initrd that was installed, and it had a /lib/
that was a soft link to  The initrd that I created had the but failed to have the soft link for it.

Version-Release number of selected component (if applicable):
# mkinitrd --version
mkinitrd: version 6.0.8

How reproducible:

Steps to Reproduce:

1. run mkinitrd
Actual results:
Failed to create the necessary softlinks.

Expected results:
Create all the necessary files.

Additional info:

Comment 1 Steven Rostedt 2007-03-21 13:01:37 UTC
I also just noticed that the created initrd has:

  lib/ -> /lib/
  but not

where as the working initrd has

  lib/ -> /lib/
  but not the

No other files are missing in the /lib directory

Comment 2 Bug Zapper 2008-04-04 06:36:40 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 3 Bug Zapper 2008-05-06 19:23:32 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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