So if you're doing a full-upgrade/dist-upgrade be careful!
Grub changes his behavior.
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 +0100So 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:
su
echo -e '\n# enable OS_PROBER\nGRUB_DISABLE_OS_PROBER=false' >> /etc/default/grub
update-grub
Danke für die Warnung und die Lösung . Funktioniert.
Thanks, Works fine.
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.
+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
Zitat von: 467-472The 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
Zitat von: 625-634The 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.
Zitat von: 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 ...'
(just FYI to see other opinions)
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
Imho manually creating boot entries is too difficult for lesser skilled users as orinoco already mentioned.
If auto-detection of other OSes is a security risk a good middle ground between auto-detection and manual creation of boot entries would be some kind of interactive tool/script to create a boot entry file to put it into /etc/grub.d/ maybe something similar to a debconf dialogue.
Just my 2 cents ;-)
It's such a security risk that Debian Stable still allows the OS prober to function...okay, got it (sarcasm).
Englisch-Deutsch mit freundlicher Genehmigung von Google Translate:
Es ist ein solches Sicherheitsrisiko, dass Debian Stable dem OS-Prober immer noch erlaubt zu funktionieren ... okay, verstanden (Sarkasmus).
Just looking for a place to thank you for this distro. I have done a few installs on both intel and AMD machines with good results. I used to use a rolling distro and KDE some years ago but kde seemed to move in a direction I was not interested in and the distros offering a rolling testing seemed to dry up. Then I found this distro through distrowatch and decided to try it with kde to see where things have gone. Boy what a great surprise. I work in radio with media files and do a lot of bash scripting etc. This has been a god send for me. I have been careful with repositories (a lesson hard learned) using only debian multimedia testing as extra repos and have had zero problems thus far. Thanks again.
Ben
Hi ben, glad you like it.