Bug 466298

Summary: Feature request: implied kernel version
Product: [Fedora] Fedora Reporter: Ian Collier <imc>
Component: mkinitrdAssignee: Peter Jones <pjones>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: medium    
Version: 9CC: dcantrell, pjones, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-06 15:47:38 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 Ian Collier 2008-10-09 16:17:39 UTC 
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 15:47:38 UTC 
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