2f7d9c9f78
This is a 277K (as of right now) addition that can greatly help in some last recourse scenarios. The specific rEFInd setup will not be able to boot the installer image, but this is not why it has been added. It has been added to make use of its volumes scanning capabilities to boot existing EFI images on the target computer, which is sometimes necessary with buggy EFI. While is isn't NixOS's job to fix buggy EFI, shipping this small bit with the installer will help the unlucky few. Example scenario: two wildly different EFI implementation I have encountered have fatal flaws in which they sometimes will lose all the settings, this includes boot configuration. This is compounded by the fact that the two specific and distinct implementation do not allow manually adding ESP paths from their interface. The only recourse is to let the EFI boot the default paths, EFI/boot/boot{platform}.efi, which is not a default location used by the NixOS bootloaders. rEFInd is able to scan the volumes and detect the existing efi bootloaders, and boot them successfully. |
||
---|---|---|
.. | ||
channel.nix | ||
installation-cd-base.nix | ||
installation-cd-graphical-gnome.nix | ||
installation-cd-graphical-kde-new-kernel.nix | ||
installation-cd-graphical-kde.nix | ||
installation-cd-minimal-new-kernel.nix | ||
installation-cd-minimal.nix | ||
iso-image.nix | ||
sd-image-aarch64.nix | ||
sd-image-armv7l-multiplatform.nix | ||
sd-image-raspberrypi.nix | ||
sd-image.nix | ||
system-tarball-fuloong2f.nix | ||
system-tarball-pc-readme.txt | ||
system-tarball-pc.nix | ||
system-tarball-sheevaplug.nix | ||
system-tarball.nix |