href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 4/19/2012; last Web page update:
-9/19/2015, referencing rEFInd 0.9.2</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<tt>refind_linux.conf</tt> file. Without the first of these options,
rEFInd could not locate my kernel; and without the second, the boot
failed with a message to the effect that the initial RAM disk could not
- find <tt>/sbin/init</tt>.</li>
+ find <tt>/sbin/init</tt>. rEFInd 0.10.0 adds <tt>@/boot</tt> as a
+ standard option to <tt>also_scan_dirs</tt>, and its
+ <tt>refind-install</tt> and <tt>mkrlconf</tt> scripts should pick up
+ the root flags, assuming the system is booted into the regular
+ installation. These additions make it easier to set up rEFInd to work
+ with Btrfs.</li>
<li><b>ISO-9660</b>—This driver originated with rEFIt's author, but
he never released a final version. Its code was improved by Oracle for
one can be helpful; however, you may need to install it on your hard
disk before you can read an optical disc.</li>
-<li><b>HFS+</b>—Oracle seems to have written this driver, apparently
- with some code taken from open source Apple examples. It was then
- further modified by the Clover authors. I expect this driver to have
- limited appeal to most rEFInd users. Macs don't need it, since Apple's EFI
- implementation provides its own HFS+ driver, and HFS+ isn't normally
- used on UEFI-based PCs. Some CDs are mastered with both ISO-9660 and
- HFS+, or even with HFS+ alone, and it's conceivable that an HFS+ driver
- would be useful when accessing such discs. I'm providing the driver
- mainly because it compiled cleanly with no extra work, aside from
- providing a Makefile entry for it.</li>
+<li><b>HFS+</b>—Oracle wrote this driver, apparently with some code
+ taken from open source Apple examples. It was then further modified by
+ the Clover authors. I expect this driver to have limited appeal to most
+ rEFInd users. Macs don't need it, since Apple's EFI implementation
+ provides its own HFS+ driver, and HFS+ isn't normally used on
+ UEFI-based PCs. Some CDs are mastered with both ISO-9660 and HFS+, or
+ even with HFS+ alone, and it's conceivable that an HFS+ driver would be
+ useful when accessing such discs. Also, one unusual feature of this
+ driver is that it can read files from within an Apple LVM setup, which
+ Apple's own EFI HFS+ driver can't do. The upshot of this feature is
+ that if you load this driver on a Mac that uses Apple's LVM, rEFInd is
+ likely to show two OS X boot options. Ordinarily this is pointless, but
+ it could be helpful if your Recovery HD volume becomes damaged. I'm
+ providing the driver mainly because it compiled cleanly with no extra
+ work, aside from providing a Makefile entry for it.</li>
<p class="sidebar"><b>Warning:</b> I've received multiple reports of system hangs when using the NTFS driver; however, I've been unable to replicate the problem. (The problem is probably triggered either by interactions with specific EFIs or by unique features of the "problem" NTFS volumes.) I therefore recommend avoiding it unless it's absolutely necessary. I've added a couple of checks to the driver code in rEFInd 0.9.1 that <i>may</i> fix this problem, but these checks may also have no effect.</p>
<p>When you reboot after installing drivers, rEFInd should automatically detect and use the drivers you install. There's likely to be an extra delay, typically from one to five seconds, as rEFInd loads the drivers and tells the EFI to detect the filesystems they handle. For this reason, and because of the possibility of drivers harboring bugs, I recommend installing only those drivers that you need. If you like, you can install drivers you don't plan on using to some other directory, such as <tt>/drivers</tt> on the ESP's root. You can then load these drivers manually with the EFI shell's <tt>load</tt> command if the need arises in the future. You can then tell the shell to re-assign drive identifiers with <tt>map -r</tt>:</p>
<pre class="listing">
-fs0: <tt class="userinput">load reiserfs_x64.efi</tt>
+fs0: <tt class="userinput">load btrfs_x64.efi</tt>
fs0: <tt class="userinput">map -r</tt>
</pre>