ahmza
fc1772e5db
grub.enable defaults to true, so adding a boot.loader block silently switched this host from the systemd-boot it was installed with over to grub. nixos removes neither the old bootloader's files nor its nvram entry, so both lived on the esp and the firmware kept booting a frozen systemd-boot menu. pinning both options means a conflicting definition elsewhere now fails loudly instead of quietly winning. note the pins delete nothing - stale EFI/systemd/, loader/ and the leftover nvram entry still have to be cleared by hand. done on shadow, not verified on t480. configurationLimit bounds esp usage for real, not just the menu: install-grub.pl unlinks any $boot/kernels/* that no kept generation references. sizing measured on shadow rather than assumed - 10 kept generations referenced 1 bzImage and 3 initrds for 114mib total, about 11mib per generation, because generations share aggressively. the worst case is higher, around 47mib each, since nixpkgs embeds /etc/modprobe.d/nixos.conf inside the initrd and so every kernel module parameter edit mints a fresh one. 10 therefore costs ~115mib typically and ~470mib worst case against a 1gib esp that also carries the grub modules, the catppuccin theme, and windows' own boot files. keeping it conservative matters because overflow fails as `copy ... or die` in install-grub.pl, which runs *after* the system profile has already been switched - the result is an activated but unbootable generation. t480 reaches this module too and its esp may be smaller.