Indeed... "removable" isn't necessarily a well-defined concept. If I knowingly use a USB HDD for the rootfs, it is "removable"? [discuss]
However, if a _new_, previously unknown bootable target appears, this means: * it happened by accident or malice, * the administrator did it on purpose and almost certainly Knows What They're Doing, or * bus renumbering / device renaming etc. happened (do we need to worry about this possibility?) Some options might be: * during automated upgrades, do not change the set of boot targets: but we can and remove kernels seen in the standard distro locations, and can update the boot configuration for existing targets generally: since the installer or admin already signed off on each target being trusted to boot the system. * when manually running update-grub at least print a warning, and possibly require the user to explicitly say "yes" to something before adding a new boot target or something which looks fishy or unintentional * ...or even, require the admin to edit the grub config manually for this and don't attempt to automate addition and removal of weird devices. Since only experienced users will be affected anyway, this may be reasonable (bad assumption?) For this kind of case, I'd tend to expect to have to edit the grub config at least once... but maybe I'm too old-school. -- update-grub should not automatically configure booting from removable devices? https://bugs.launchpad.net/bugs/644206 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
