Felix Miata changed bug 1101756
What Removed Added
Flags needinfo?(mrmazda@earthlink.net)  

Comment # 5 on bug 1101756 from
(In reply to Josef Reidinger from comment #4)
> Well, we consider this "expert" option. We already discussed it in past and
> problem is during upgrade to refresh it properly, which e.g. for opensuse
> does not work well with tumbleweed

What's the problem just using it if user has modified GRUB_DISTRIBUTOR= to
anything that has never been in a /etc/default/grub.rpmnew file? As it is
fairly common for TW users to also be Leap users, maybe TW should have a
different default GRUB_DISTRIBUTOR= than Leap, at least on UEFI installations?

> or when using zypper dup for leap switch.

As an expert option, I should think sufficient a relnote that the multibooter
admin needs to address this. Multibooters do expect some foibles due to
configurations that QA can't test programmatically.

> So because it is expert option, what should be possible to do, is to set it
> manually and then yast2 will ( should ) respect it and keep it as it was
> done by manual edit.

> Does it make sense?

Depends on your meaning of manual I suppose. Simple presence of a non-standard
GRUB_DISTRIBUTOR= on the target ought to be sufficient if it's an upgrade. If a
new install, have linuxrc accept cmdline parameter e.g.
GRUB_DISTRIBUTOR=os151p11 to incorporate in Grub2 installation, and/or as I
tried, using vtty2 while installation proceeds, or even before installation to
already formatted / starts, to put GRUB_DISTRIBUTOR=os151p11 in the target's
/etc/default/grub for incorporation.

Adding an input box on the bootloader options tab that defaults to opensuse and
rejects any string that is found as a directory name on a current ESP partition
root, unless it matches GRUB_DISTRIBUTOR= in /etc/default/grub if an upgrade, I
would think doable as well.


You are receiving this mail because: