Bug 466298 - Feature request: implied kernel version
Feature request: implied kernel version
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: mkinitrd (Show other bugs)
9
All Linux
medium Severity low
: ---
: ---
Assigned To: Peter Jones
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-09 12:17 EDT by Ian Collier
Modified: 2009-05-06 11:47 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-05-06 11:47:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ian Collier 2008-10-09 12:17:39 EDT
Description of problem:
I frequently find myself having to run mkinitrd from the Fedora rescue disc in order to port an existing Fedora installation over to new hardware.

I type "mkinitrd -f /boot/i" and then the TAB key, then maybe one digit and TAB again, so now I have "mkinitrd -f /boot/initrd-2.6.26.3-29.fc9.x86_64.img".  So far so good.

But now mkinitrd requires me to type out "2.6.26.3-29.fc9.x86_64" using my fingers (no cut-and-paste in rescue mode).  This seems somewhat redundant to me, not to mention error-prone.

It would save a lot of time if initrd, seeing that the image file is called "initrd-XYZ.img", would look for kernel version XYZ if I didn't specify one explicitly.  Of course if the image file isn't called that then mkinitrd would still require an explicit kernel version.
Comment 1 Jeremy Katz 2009-05-06 11:47:38 EDT
mkinitrd isn't going to grow this functionality, but dracut (which will hopefully be replacing mkinitrd in Fedora 12) already has this sort of thing

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