Not sure anyone is interested but FYI…
One other interesting thing regarding the messy workaround above… Please note I am still just testing these in a VM. I’m guessing this will all change at some point in the future so use at your own risk! This is all based on NixOS 24.05.
- The default sort order is descending, so (within a generation) an EFI file which starts with the letter Z will display before an EFI file with the letter A and the default seems to always be the first file in the latest generation. This led to another crude workaround which allows a specialisation to be set as the default boot entry even with secure boot in use.
My current secure boot menu on my test VM looks like this, with the specialisation named ‘testA’ set as the default boot option. Note the moment specialisations are enabled, the default label changes from (Linux a.b.cc) to (Linux a.b.cc) (Generation d, Built on yyyy-mm-dd) {efi-filename). For the Generation 6 boot entry below, I manually appended the generation number and build date to the label. Even though the boot entries support whitespace, the nixos-system-label doesn’t, hence the underscores.
NixOS Uakari Enable_specialisations__ (Linux 6.6.51) (Generation 7, Built on 2024-10-18) (x_testa___
NixOS Uakari Enable_specialisations__ (Linux 6.6.51) (Generation 7, Built on 2024-10-18) (o_testabce
NixOS Uakari Enable_specialisations__ (Linux 6.6.51) (Generation 7, Built on 2024-10-18) (o_base____
NixOS Uakari No_specialisations_enabled__________________________Generation_6_18Oct24 (Linux 6.6.51)
Reboot Into Firmware Interface
I have asked about a more formal solution on the lanzaboote section of github.