http://bugzilla.suse.com/show_bug.cgi?id=997322
http://bugzilla.suse.com/show_bug.cgi?id=997322#c9
--- Comment #9 from Josef Reidinger
(In reply to Josef Reidinger from comment #7)
I expect issue Olaf have is that yast2 set this value at the end of installation, so if any part of rpm post install script call grub2-mkconfig, it will use default and default is to disable os_prober. So it is by default disabled on SLES, but only at the end of installation.
It would be cool if yast would write /etc/default/grub upfront.
I causes series of problems in past, like e.g. when /etc/default/grub get new option, then config written by yast missing it and there is no easy way for user to modify it as it is not there at all. Also not all options are configured by yast2 so it will be missing. Well, perfect solution would be to adapt it just after grub2 install, but it is not possible now. So we do not it the end.
This would also fix the bug that yast in inst-sys reports an error if that file is not there, in case grub2 was not installed by accident.
if yast2 is not installed, then you have more serious problem and any error report is good.
I guess it just tries to modify an existing file, instead of writing out the configured settings. I think any defaults should go into the code, instead of a config file.
YaST2 modify existing file, as it allows us to configure only option where we are interested, keep upstream config option comments and other stuff. From my POV, defaults should be in config file and not in code. Code just do more complex proposal that need to know e.g. storage setup, product or architecture specific stuff. -- You are receiving this mail because: You are on the CC list for the bug.