http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c9 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |estellnb@gmail.com --- Comment #9 from Josef Reidinger <jreidinger@novell.com> 2010-07-14 11:45:33 UTC --- (In reply to comment #8)
Just tested it, but... if I update /etc/sysconfig/bootloader - nothing happens. Running update-bootloader --refresh - nothing happens.
Of course, refresh is just to install bootloader to its location. It doesn't change configuration.
I have to either update a kernel to add these options or edit both /etc/sysconfig/bootloader AND /boot/grub/menu.lst which is suboptimal.
So either don't remove custom automatically, try to detect them: if it's different from what's defined in /etc/sysconfig/bootloader, find out custom options and add them with the new kernel.
/etc/sysconfig/bootloader is parameters for newly installed kernels. /boot/grub/menu.lst is actual settings. I detect custom settings, but if defined variables in sysconfig I use it. It is because we want clear solution for customer, because in past sometime happen that when customer has different kernel favors with different options and we use bad parameters for newly added kernel, so we use solution where is clear which parameters is used for new kernels.
Or provide a command to update the bootloader.
tool to edit bootloader is yast. Pbl is library, so you can create own tool using it. It is opensource.
Or use yast
But this is not a good solution - people cried for years that you can only configure your system using yast; editing configuration files will break your system. This has become much better recently, but now it returns in a very critical place: the bootloader.
So do we really want to return to "use yast or die"?
It is not "use yast or die". It is edit menu.lst for current kernels and edit /etc/sysconfig/bootloader for newly installed kernels ( e.g. ubuntu has both in one file and it is horrible mess, so we have two files ) None solution is the best one, always there is some users which complain. I hope that current solution is flexible and text in menu.lst should help user to know what is needed to edit to preserve settings after adding new kernel. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.