http://bugzilla.suse.com/show_bug.cgi?id=994322 http://bugzilla.suse.com/show_bug.cgi?id=994322#c9 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jreidinger@suse.c | |om) | --- Comment #9 from Josef Reidinger <jreidinger@suse.com> --- (In reply to Steffen Winterfeldt from comment #7)
I would not do it via symlinks; that's likely to create a mess at some point during package updates. Also, it's impractical if some tool needs to determine the current state.
It might be a good opportunity to cut the line and move remaining config vars out of grub_installdevice into /etc/sysconfig/bootloader. grub_installdevice is not, as its name suggests, some file used by the regular grub. So we can as well go the common SUSE-way of using /etc/sysconfig.
In this case, say, bootloader::DESTINATION with values like 'disk', 'boot', 'root'.
We might put comment 4 into sp2 as it doesn't change the way things work currently and only steps in if grub_installdevice is obviously invalid. But for that I'd like some feedback also from Josef and particularly Olaf as to whether this actually helps.
Well, in past we try to reduce content of /etc/sysconfig/bootloader because it confuse users of other distribution which have everything in upstream files. So even for this case I suggest to check how do it other distributions? What they do if there is update in grub2 stage1 code? how they recognize in which location it should install it? I am sure RHEL, ubuntu and others have to have way how to do it, so if they use some common place, we should also use it to not confuse our users. -- You are receiving this mail because: You are on the CC list for the bug.