On 16/10/2018 07.32, David C. Rankin wrote:
On 10/15/2018 06:46 PM, Carlos E. R. wrote:
On 16/10/2018 00.41, David C. Rankin wrote:
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".
Oh, Sorry Carlos, I mean I commented the following:
### BEGIN /etc/grub.d/30_os-prober ### # menuentry 'Windows 10 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-6C1A63A81A636E50' { # insmod part_msdos # insmod ntfs # set root='hd0,msdos1' # if [ x$feature_platform_search_hint = xy ]; then # search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 6C1A63A81A636E50 # else # search --no-floppy --fs-uuid --set=root 6C1A63A81A636E50 # fi # parttool ${root} hidden- # drivemap -s (hd0) ${root} # chainloader +1 # } ### END /etc/grub.d/30_os-prober ###
Why would that cause the entry to be changed?
Notice that that file can be replaced by an update. There you have the reason for your problem. Just edit "/etc/default/grub" -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)