Bug 183917

Description of problem:
This is realated to the whole kdump thing.  

After installing/uninstalling a kdump kernel, we need a way to add/remove
arguments to the normal kernel.  An example:

%post kdump
[ ! -x /usr/sbin/module_upgrade ] || /usr/sbin/module_upgrade
%{rpmversion}-%{release}-kdump
/sbin/new-kernel-pkg --package kernel-kdump --mkinitrd --depmod --install
%{KVERREL}kdump
+/sbin/new-kernel-pkg --args="crashkernel=64M@16M" --update %{KVERREL}

(notice the missing kdump after %{KVERREL})
This is needed to allow the first kernel to create a memory hole (given as the
argument) in which to place the second kernel (and initrd) into.  Of course the
machine still needs to be rebooted to utilize this new parameter, *sigh* (a
hurdle for another day).  

In addition this would allow us to do the opposite upon uninstalling (%post-un):

+/sbin/new-kernel-pkg --remove-args="crashkernel=64M@16M" --update %{KVERREL}

That is the crux of the problem.  I have attached a patch against
new-kernel-pkg, which solves the problem in one way, but I leave you to be the
judge of what is the most appropriate way.  



Version-Release number of selected component (if applicable):
mkinitrd-5.0.29

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Thanks for the patch.  This is in 5.0.33-1 , which should be in tomorrow's rawhide.