----- Original Message -----
Am 14.05.2012 20:46, schrieb Tim Nelson:
Greetings-
I have a few custom kernel parameters being passed to a CentOS box via the /boot/grub/grub.conf file. However, if there is a kernel update, and grub.conf is regenerated, how do I ensure my custom parameters are:
a. left in place on the older kernels b. added to the new kernel?
what exactly is your problem?
the params of the newest kernel in the grub-config is taken by grubby since many years - this is a redhat OS not ubuntu!
So, to confirm, any parameters specified in the grub.conf for the current kernel will be copied over to the new kernel entry? I do see an option to grubby, specifically '--copy-default' which appears to do the necessary work. This is called when the new kernel is installed (yum/rpm)?
--Tim
----- Original Message -----
----- Original Message -----
Am 14.05.2012 20:46, schrieb Tim Nelson:
Greetings-
I have a few custom kernel parameters being passed to a CentOS box via the /boot/grub/grub.conf file. However, if there is a kernel update, and grub.conf is regenerated, how do I ensure my custom parameters are:
a. left in place on the older kernels b. added to the new kernel?
what exactly is your problem?
the params of the newest kernel in the grub-config is taken by grubby since many years - this is a redhat OS not ubuntu!
So, to confirm, any parameters specified in the grub.conf for the current kernel will be copied over to the new kernel entry? I do see an option to grubby, specifically '--copy-default' which appears to do the necessary work. This is called when the new kernel is installed (yum/rpm)?
As a follow up... I just tested this and can confirm the parameters are indeed copied from the existing entries to the new kernel entry.
Thanks for the info.
--Tim
-
Tim Nelson