Hi, > This is working as intended. I do not want to install gummiboot before > they had the chance to properly configure it, and it also introduces > other issues. Some users also may not want to install gummiboot to the > ESP at all, and just want the binary for a USB stick or similar.
Fair enough. However: - It would be awesome if you could document this in a README.Debian. - On my system, I got an error message when first installing gummiboot because update-gummiboot was unable to determine the root partition. My first impression was that the postinst script was trying to install the boot loader to the EFI partition and failed. It might make sense to check in the postinst script whether gummiboot is installed at all (e.g. by invoking "gummiboot status") and if it isn't, the script should not try to update it. The use case you've named (manual installation on a USB stick but not on the system disk) is a good example where the postinst script should *not* automatically copy the kernel and initrd to the EFI partition of the system disk. > > - gummiboot offers the option "--no-variables" which prevents changes to > > the EFI boot order. One example where this option comes in handy is a > > dual-boot Mac on which the user wants to continue booting OS X by default. > > The patch makes this option configurable. I've set the priority to > > "critical" because changing the boot order can break the system. > This problem only arises due to calling install. That doesn't seem to be true, from looking at src/setup/setup.c it looks like gummiboot is added to the EFI variables even in update mode, albeit to the *end* of the boot order list. Kind regards, Lukas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
