Re: UEFI multiboot control usurped with each kernel update

[Felix Miata]

Pascal Hambourg composed on 2018-10-18 07:33 (UTC+0200):

> Felix Miata composed:

>> Felix Miata composed on 2018-08-09 01:10 (UTC-0400):

>>> With 3 distro installations on one disk, each OS as a kernel update is 
>>> installed
>>> updates NVRAM to make its entry in the ESP partition top priority. How can I
>>> stop that from happening, so that my choice of priority remains first 
>>> instead of
>>> me needing to remember before shutdown or reboot to run efibootmgr to put it
>>> back like it was before the kernel update? I don't want to prevent the 
>>> update
>>> from creating a new /boot/grub/grub.cfg, only from usurping boot priority.

> What are these distributions ? The ones I know use GRUB EFI and 
> reinstall it only when installing or updating GRUB packages, not when 
> installing or updating a kernel. The latter just requires updating grub.cfg.

Tumbleweed is the one I want in control.
Leap 15.0, Bionic and Buster are the usual usurpers, but TW steals it back if I 
leave
it with a thief.

Grub2 familiarity here is two UEFI PCs, one Asus (AMI Aptio 2018-05-11), other 
Gigabyte
(AMI F9 2018-04-10), both Kaby Lake. All my 25+ other PCs boot IBM compatible 
MBR code
and Grub Legacy and/or IBM Boot Manager on a primary partition.

>> What I've been doing is commenting out the EFI partition line in fstab of 
>> all distros except the
>> one I wish to retain boot priority in NVRAM. So far it seems to be effective 
>> in preventing
>> updates usurpation. Can anyone think of reason(s) why this might be a bad 
>> idea? So far, I've
>> come up with nothing.

> It seems that grub-install aborts immediately if the EFI partition is 
> not mounted, so it should be fine if all distributions use GRUB.-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/