On 10/14/2018 04:30 AM, Carlos E. R. wrote:
os-prober was installed automatically when Leap 42.3 was installed, but has been well-behaved up until these 2018-10-02 updates. Why was this changed?
Is it better to rpm -e os-prober? Or, can /etc/default/grub be trusted not to be overwritten so that GRUB_DISABLE_OS_PROBER="true" will be respected going forward?
If you do not want os-prober to run, you have to disable it. That entry in grub config should work; has worked for me always.
Otherwise an update of grub, which I think usually triggers a grub rerun, will also do an os-prober run-
:) err, umm 42.3 like I said above (but granted, I could have done a zypper dup in the interim) Yes, I understand the grub rerun. What I don't understand is why for over a year of grub reruns, os-prober never included the Win10 boot entry until the last rerun. I recall a thread in the last couple of weeks where somebody complained that windows wasn't added, so I suspect there was a change made that now automatically causes it to run os-prober, but this is wrong as it will overwrite your windows bootloader if you are booting MBR from /dev/sda for both Windows and Linux. That is what prompted my question of "What changed in the Oct. 2, 2018 update to grub2 so as to invoke os-prober causing it to populate grub.cfg with the Windows entry. More importantly, if this is desired behavior now, will GRUB_DISABLE_OS_PROBER="true" be respected and not overwritten by subsequent grub2 updates, or should I just rpm -e os-prober to make sure? -- David C. Rankin, J.D.,P.E.