Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Thanks for the great answer! A quick question (and I can ask this in a separate one if you like): based on your first tip, I could have just mounted to the existing boot partition (i.e., /dev/sda2) and nixos-install would only have added another EFI executable, correct? And if boot.loader.efi.canTouchEfiVariables had been set to false, I could've just used Ubuntu's GRUB and have an extra entry set up for NixOS? Commented May 29, 2018 at 2:53
  • I guess the answer is yes: How to configure dual boot NixOS with Mac OS X on an (U)EFI MacBook? and NixPkgs issue #21534 - Option to add extra entries to systemd-boot Commented May 29, 2018 at 5:41
  • 1
    Yep, that's correct. I've dual-booted NixOS with both MacOS and Windows 10 and in both cases I shared the same ESP (EFI partition). Setting boot.loader.efi.canTouchEfiVariables to false should tells the installer to leave your current boot manager (GRUB2) as the default. Then it's a matter of adding systemd-boot to GRUB2 as an item. Another way, especially if you have a lot of systems, is to install rEFInd and let it be the default. rEFInd checks your ESP for EFI executables and lists them, so you don't have to keep adding menu entries. Commented May 29, 2018 at 17:07