Siduction Forum > Upgrade Warnings
New grub disabled OS_PROBER by default
hendrikL:
So if you're doing a full-upgrade/dist-upgrade be careful!
Grub changes his behavior.
--- Code: ---zcat /usr/share/doc/grub-common/NEWS.Debian.gz
grub2 (2.06-1) UNRELEASED; urgency=medium
* Boot menu entries for other operating systems are no longer generated by
default. To re-enable this, set GRUB_DISABLE_OS_PROBER=false in
/etc/default/grub.
-- Colin Watson <cjwatson@debian.org> Wed, 18 Aug 2021 13:03:23 +0100
--- End code ---
So if you are getting trouble because of this, do the following (maybe best before rebooting)
* Become root
* edit /etc/default/grub and insert GRUB_DISABLE_OS_PROBER=false
* run update-grub
Or do following, it's the same but faster:
--- Code: ---su
echo -e '\n# enable OS_PROBER\nGRUB_DISABLE_OS_PROBER=false' >> /etc/default/grub
update-grub
--- End code ---
michaa7:
Danke für die Warnung und die Lösung . Funktioniert.
Thanks, Works fine.
tranquil:
Since the OS prober was enabled by default, I wonder why the decision was made to disable it by default with the new release. Not a good way to implement such a change in my opinion.
der_bud:
+1, I thought the same, found that some on IRC #debian-next pointed to https://salsa.debian.org/grub-team/grub/-/blob/master/ChangeLog, especially lines 467-472 and 625-630
--- Quote from: 467-472 --- The default was GRUB_DISABLE_OS_PROBER=false if you don't set
GRUB_DISABLE_OS_PROBER at all. To prevent os-prober from starting we
have to set it by default to true and shuffle GRUB_DISABLE_OS_PROBER to
code section, which is executed by the script. However we still give an
option to the user to overwrite it with false, if he wants to execute
os-prober after all.
Fixes: e3464147
--- End quote ---
--- Quote from: 625-634 --- The os-prober is enabled by default what may lead to potentially
dangerous use cases and borderline opening attack vectors. This
patch disables the os-prober, adds warning messages and updates
GRUB_DISABLE_OS_PROBER configuration option documentation. This
way we make it clear that the os-prober usage is not recommended.
Simplistic nature of this change allows downstream vendors, who
really want os-prober to be enabled out of the box in their
relevant products, easily revert to it's old behavior.
--- End quote ---
--- Quote from: IRC# --- '... "This way we make it clear that the os-prober usage is not recommended." -- which I also agree with, one should manually make an entry for other oses vs try to auto detect them ...'
--- End quote ---
(just FYI to see other opinions)
orinoco:
This might be an issue for not skilled dual-boot users who want to migrate softly from one to the better os. Installers should handle this with a proper dialog.
Bad persons will say that this is the late revenge from overriding the bootblock...
Just my 2c
Navigation
[0] Message Index
[#] Next page
Go to full version