On 16/10/2018 00.41, David C. Rankin wrote:
On 10/15/2018 07:45 AM, Carlos E. R. wrote:
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? I expect that variable to be obeyed. I don't know if I have applied that update to my machines having Windows, so I'll find out later.
Yes, and this is somewhat a typical setup. I have win10 on sda and opensuse on sdb. I do not want grub2 or any bootloader messing with sda. I specifically installed opensuse on sdb with grub2 in the mbr of sdb to prevent any hint of the Linux install being visible should somebody steal by laptop. So to reach sdb to boot I use the bios selection to boot from sdb. It is pointless to have os-prober put a windows entry in grub.cfg for just that reason. The only way I get to grub is to choose a custom boot option.
Why not simply encrypt the disk?
Ever since I installed 42.3, there has been no issue of os-prober putting windows in grub.cfg, but starting with my last update and the updated grub2 package, os-prober now inserts windows for some bewildering reason.
To get rid of what os-prober added, I just commented the entry out in grub.cfg, but I would like to avoid having to do that again. If it is not an initial install, os-prober shouldn't be adding anything unless it is specifically told to do it.
No, that should not work. Set it to TRUE. Commenting the entry sets default value, which appears to be "false". -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))