On Fri, 7 Sep 2018 15:57:48 +0200 Raphael Hertzog <hert...@debian.org> wrote: > Control: tags -1 + patch > > On Fri, 07 Sep 2018, Raphaël Hertzog wrote: > > The problem seems to come down to the fact that during initial installation, > > (at least) when the install picks the new *-signed packages, they get > > installed to /EFI/kali but the binary installed inside is actually > > expecting the configuration file in /EFI/debian/grub.cfg. > > I'm attaching a possible patch. I checked that the package builds, but I > did not test the resulting package. > > Since the EFI image hardcodes the patch in the EFI partition, I modified > /etc/default/grub to contain GRUB_BOOTLOADER_ID initialized with the > value of SB_EFI_VENDOR coming from debian/rules. grub-install has been > patched to initialize the default value of its --bootloader-id parameter > with this variable. > > I opted to not modify GRUB_DISTRIBUTOR since this contains the > user-visible name of the derivative and we want to keep that obviously. > > Cheers, > > PS: I pushed my branch here too: https://salsa.debian.org/hertzog/gru b
Hi Raphael,
Maybe the changes could be simplified a bit by using the Efi-Vendor
package metadata that was added in the same version?
Something like this might work:
dpkg-query -f='${Efi-Vendor}' -W @PACKAGE@-bin
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
