I recently released rEFInd version 0.8.4. A summary of changes appears on the revisions page, but I wanted to highlight two important changes:
Because of changes in OS X 10.10 (Yosemite), the install.sh script now installs rEFInd to the ESP by default under OS X, using the filename EFI/BOOT/bootx64.efi (or EFI/BOOT/bootia32.efi on 32-bit systems). I've also changed the dont_scan_volumes default in the program itself. The end result is that rEFInd should install more cleanly on Macs running Yosemite (or using whole-disk encryption, for that matter). The downside is that if you've got an existing installation to the previous default location and want to update it, you'll need to either use the new --notesp option to install.sh or accept the new location and manually delete the old installation to keep it out of your menu. There may also be problems with 30-second delays in the boot process, although my hope is that using the fallback boot loader name will minimize these problems.
Thanks to a submission from Rohan Sehgal, rEFInd has experimental support for network booting. This support relies on separate iPXE binaries. When these are installed and appropriate changes are made to scanfor and/or showtools, rEFInd can boot from a network source. This support is still very new and has known bugs, though. It's crashed two test computers and has pulled down BIOS-mode binaries rather than EFI-mode binaries from some servers. Nonetheless, it works well enough that it might be useful for some people. If you need this support, you'll have to build the iPXE binaries yourself. The BUILDING.txt file in the rEFInd source package describes how to do this. If you don't need network-boot support, don't worry; it's disabled by default, and even when enabled, it relies on those binaries, so you shouldn't experience the problems I've just described.
I advise OS X users to weigh their needs with respect to Yosemite and boot program locations before upgrading. A rEFInd upgrade can be done smoothly, but it's safest if you know where your existing rEFInd is installed and where it should be installed if and when you upgrade to Yosemite.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I recently released rEFInd version 0.8.4. A summary of changes appears on the revisions page, but I wanted to highlight two important changes:
install.shscript now installs rEFInd to the ESP by default under OS X, using the filenameEFI/BOOT/bootx64.efi(orEFI/BOOT/bootia32.efion 32-bit systems). I've also changed thedont_scan_volumesdefault in the program itself. The end result is that rEFInd should install more cleanly on Macs running Yosemite (or using whole-disk encryption, for that matter). The downside is that if you've got an existing installation to the previous default location and want to update it, you'll need to either use the new--notespoption toinstall.shor accept the new location and manually delete the old installation to keep it out of your menu. There may also be problems with 30-second delays in the boot process, although my hope is that using the fallback boot loader name will minimize these problems.scanforand/orshowtools, rEFInd can boot from a network source. This support is still very new and has known bugs, though. It's crashed two test computers and has pulled down BIOS-mode binaries rather than EFI-mode binaries from some servers. Nonetheless, it works well enough that it might be useful for some people. If you need this support, you'll have to build the iPXE binaries yourself. TheBUILDING.txtfile in the rEFInd source package describes how to do this. If you don't need network-boot support, don't worry; it's disabled by default, and even when enabled, it relies on those binaries, so you shouldn't experience the problems I've just described.I advise OS X users to weigh their needs with respect to Yosemite and boot program locations before upgrading. A rEFInd upgrade can be done smoothly, but it's safest if you know where your existing rEFInd is installed and where it should be installed if and when you upgrade to Yosemite.