Although refind is good, there seems to be an awful lot missing from the instructions page, it could do with being proofread by someone other than the author so that all the dozens of "what does that mean?" or "where's that located?" questions can be answered right at the start. What's obvious to someone writing the program may not be so obvious to those trying to use it.
Anyway, to find its proper location I managed to find some clues in the uninstall portion of the instructions. These point back to the manual installation guide for instructions on mounting the unmounted EFI partition, et voila!
diskutil list to get a list of partitions, in my case EFI is disk0s1.
mkdir /Volumes/esp to create somewhere to mount the volume to.
sudo mount -t msdos /dev/disk0s1 /Volumes/esp to mount the volume.
Now look in /Volumes/esp/EFI/refind to find your refind.conf file. Alternatively Finder will now have mounted a disk called EFI in your Devices list on the left-hand-side, so you can click on that and browse to EFI/refind.
Googling for the answer found this page so hopefully this little snippet of info will be useful for others trying to track it down.
I spend the last 3 nights searching every corner of the web for a straightforward guide how to dualboot the latest macOS 10.12 Sierra with Ubuntu, but it seems like there is just so many ways people recommend doing, that in other forums people are advising against at.
You're running into the paradox of choice -- too many options on this matter are creating confusion. In reality, it's hard to say that any one option in this specific issue is really any better than any other option, except in fitting certain very specific goals, most of which you haven't mentioned any preferences on, except:
My ideal scenario would of course be to select either macOS or Linux via the alt-Key in Apple's standard bootloader.
In this case, the solution to which you linked makes sense, although I suspect it may be a little bit overly-complex in a couple of points. (I'm not 100% positive of that, though.)
Note, however, that the screen you see when you hold down the Alt/Option key when booting a Mac is not a boot loader; it's a boot manager. You're still relying on separate boot loaders (Apple's boot.efi file to boot macOS or GRUB to boot Linux) to boot the computer. This is, in some sense, a minor matter of terminology; but it's important to understand that boot managers are user interface tools whereas boot loaders load kernels into memory and execute them, since in some contexts this distinction is very important. Unfortunately, people tend to be sloppy about this distinction.
every new version of macOS (especially since the integration of SIP in El Capitan) appears to change the way it handles the booting process and the majority of articles regarding this subject is older than 10.11, which makes me feel a bit lost at the the moment.
Yes, the ever-changing nature of macOS booting can be a problem. I recommend you begin by ignoring anything that suggests installing Linux in BIOS/CSM/legacy mode. Although doing this is sometimes necessary, that's rarely the case today. Broadly speaking, you're then left with two choices:
- What to use as a boot manager -- Above, you expressed a preference for the Mac's built-in boot manager. This tool is limited, but you know it's already present in the computer. The two major alternatives are GRUB 2 (which is installed by Ubuntu, but I've seen few discussions of using it to boot macOS) and rEFInd (which you're obviously aware is a popular choice on Macs). rEFIt used to be a good alternative, too, but it's been abandoned for years, so rEFInd (which I forked from rEFIt) is a better choice.
- What to use as a boot loader -- Both the method you cited and any method that uses GRUB as a boot manager are likely to use GRUB as the boot loader, too. rEFInd can do the same, but rEFInd can also use the EFI stub loader, which is a kernel feature that turns the Linux kernel into its own boot loader.
Note that GRUB is both a boot manager and a boot loader. rEFInd, OTOH, is technically only a boot manager; but the existence of the EFI stub loader (which is technically a boot loader but not a boot manager) enables rEFInd to act like a boot loader of Linux kernels.
My biggest concern regarding rEFInd is the malfunctioning of the hibernation feature other users complain about.
This was a big problem a while back, but I haven't seen any recent complaints about it, so I believe that the current defaults in refind-install fix this problem. As you suggest, installing rEFInd to a separate HFS+ partition is one reported solution, so you could always try that if you install rEFInd to the ESP and then run into problems.
It's possible to switch boot managers and loaders even after you've installed everything. On this specific issue, if you decide to use rEFInd, you can hedge your bets a bit by setting aside a ~200 MiB partition. Don't even put a filesystem on it initially. Install rEFInd using its defaults, which will put it on the ESP. If you have problems, you can then put an HFS+ filesystem on the small spare partition and re-install rEFInd to it. If this resolves the problem, great. If not, you can put GRUB 2 on the small HFS+ partition in a variant of the method described in on the page to which you linked.
install Ubuntu, reformat the main Linux partition and select the swap partition (do I have to change the location for the bootloader installation?)
If the Ubuntu installer runs in EFI mode, it will install GRUB 2 to the ESP. If there's even a prompt for where to install the boot loader, it's ignored in EFI mode.
It's also worth pointing out that, if you intend to use rEFInd and the EFI stub loader, you can launch the Ubuntu installer by booting into "try before installing" mode, open a Terminal window, and typing ubiquity -b. The -b option tells the installer to not install GRUB. This will minimize the chance of a boot coup in the future, and it will prevent GRUB from running time-consuming scripts whenever the kernel is updated to modify its configuration files (which you wouldn't be using if you're not including GRUB in the boot process).
I have read that installing rEFInd on the a seperate hfs partition would fix the hibernation issue. In this case, do I have to select/reformat the little hfs partition as an EFI system partition during the Linux install (like David Anderson suggests)?
No. Technically, an ESP must use the FAT filesystem. In practice, a Mac's firmware doesn't care whether a partition is marked as an ESP or as a standard HFS+ partition when it launches a boot loader.
I should also point out that I don't see the point of creating a second ESP in the instructions to which you've linked. Maybe I'm missing something, though.
Even if would I do everything the default way (including the risk of the hibernation issue), what are the correct partition choices while installing Ubuntu? Do I need to define an new EFI system partition in this case, or not at all?
No, the ESP is intended to be shared by all the OSes on the computer. In the case of Macs, though, Apple uses it only for firmware updates, AFAIK; its boot loader resides on its Recovery HD volume.
That said, you can create multiple ESPs; doing so is legal and, AFAIK, all EFIs support such configurations. There's just little or no point to doing so.
Best Answer
Did you reinstall rEFIt manually?
If you didn't, try running this on the OSX Terminal
When prompted for your password, use the one Yosemite asks you for while trying to install new software.
After that, you should see the boot menu after you restart. When you choose to load Ubuntu from the boot menu, you may be greeted by the
grub rescue>terminal" instead of a normal boot, let me know.By the way, you can also press the option key (alt) just after you hit the power button, and there you'll see some options, including rEFIt. This has the drawback that it must be done on every boot, hence the preference for the terminal solution.