Red Hat Bugzilla – Bug 472764
let mkinitrd default to recreating the initrd for the currently running kernel
Last modified: 2014-09-15 20:23:44 EDT
Created attachment 324474 [details]
patch to add kernel and target defaults
Description of problem:
System administraters on mainframes regularily have to add some storage to the system and on mainframe you'll have to create a new initrd with the new DASD settings. One of our customers complained on the main s390-linux list that mkinitd on SLES uses those defaults whereas our mkinitd doesn't.
This might be useful on other archs, too.
Steps to Reproduce:
1. run mkinitrd without parameters -> usage info
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
Tested with RHEL5.11-Server-20140416.0.n
This will re-create the initrd in /boot for the currently running kernel.
Continue ? (y/n) y
- initrd created
- system boots
Verified that running mkinitrd without parameters recreates the initrd for the currently running kernel instead of printing usage info
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.