update-grub should not automatically configure booting from removable devices?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Expired
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: grub2
Affected: 1.98+20100804-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu maverick (development branch)
Release: 10.10
Codename: maverick
Totally by coincidence, I ran apt-get upgrade with a random card in a card reader.
The card had a maverick chroot on it (for a foreign architecture, so totally unbootable...)
Look what happens:
# update-grub
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-
Found initrd image: /boot/initrd.
Found memtest86+ image: /boot/memtest86
Found memtest86+ multiboot image: /boot/memtest86
Found Ubuntu maverick (development branch) (10.10) on /dev/sdg2
done
# cat /sys/block/
1
Even more surprising, when I rebooted, grub popped up a boot menu giving me a chance to boot that removable device (which happened to be still plugged in).
I would question whether a removable device should be magically added to the boot device list when running update-grub.
For automated upgrades, magically adding random devices which aren't part of the installation to the boot list seems undesirable/
visibility: | private → public |
Changed in grub2 (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
security vulnerability: | yes → no |
Unfortunately it's pretty much impossible to tell what's desired. Some people have a "removable" device that's actually plugged in most of the time and which contains OSes they want to boot from, and I think they'd object to GRUB not finding these any more. I can't see how to resolve both at once (even if it were configurable, there'd be debates over the default).