http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c8 Robin Knapp <robin.knapp@ts.fujitsu.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |robin.knapp@ts.fujitsu.com Resolution|FIXED | --- Comment #8 from Robin Knapp <robin.knapp@ts.fujitsu.com> 2010-07-14 13:31:41 CEST --- Just tested it, but... if I update /etc/sysconfig/bootloader - nothing happens. Running update-bootloader --refresh - nothing happens. 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. Or provide a command to update the bootloader. 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"? -- 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.