Created attachment 324336 [details] Use defaults if mkinitrd is run with no args Description of problem: Most of the time mkinitrd is run manually, it's in the form: # mkinitrd /boot/initrd-$(uname -r).img $(uname -r) With the attached patch, mkinitrd uses these values by default when run with no arguments. It provides a confirmation prompt, unless run as 'mkinitrd -f'. This is so that no action is taken for users who are accustomed to running 'mkinitrd' with no args to see the usage. 'mkinitrd --help' still shows usage. Version-Release number of selected component (if applicable): mkinitrd-6.0.52-2.fc9 Actual results: (with patch): # mkinitrd Building default /boot/initrd-2.6.25-14.fc9.s390x.img for current kernel. This file will be overwritten. Proceed? [y/N]: No changes made. Exiting. # mkinitrd Building default /boot/initrd-2.6.25-14.fc9.s390x.img for current kernel. This file will be overwritten. Proceed? [y/N]: 6 Enter 'y' or 'n'. Exiting. # ls -l /boot/initrd-$(uname -r).img -rw------- 1 root root 3677384 2008-11-21 13:41 /boot/initrd-2.6.25-14.fc9.s390x.img # date Fri Nov 21 14:24:17 EST 2008 # mkinitrd Building default /boot/initrd-2.6.25-14.fc9.s390x.img for current kernel. This file will be overwritten. Proceed? [y/N]: y # ls -l /boot/initrd-$(uname -r).img -rw------- 1 root root 3677402 2008-11-21 14:24 /boot/initrd-2.6.25-14.fc9.s390x.img # mkinitrd -f # ls -l /boot/initrd-$(uname -r).img -rw------- 1 root root 3677398 2008-11-21 14:25 /boot/initrd-2.6.25-14.fc9.s390x.img
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #0) > Created an attachment (id=324336) [details] > Use defaults if mkinitrd is run with no args > > Description of problem: > Most of the time mkinitrd is run manually, it's in the form: > # mkinitrd /boot/initrd-$(uname -r).img $(uname -r) > > With the attached patch, mkinitrd uses these values by default when run with no > arguments. Actually most of the time one wants to regenerate an initrd either for a new kernel or for a non working kernel / initrd combi. Regenerating for the current kernel makes little sense, as apparently the existing initrd does its job. Also as mkinitrd is planned to be replaced with something better (hopefully more flexible) in the future, we are not taking RFE's. Closing.