href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/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>
<input type="hidden" name="amount" value="1.00">
<input type="hidden" name="item_name" value="rEFInd Boot Manager">
<input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
-<input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
-<img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
+<input type="image" src="donate.png" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
</form>
</td>
<input type="hidden" name="amount" value="2.50">
<input type="hidden" name="item_name" value="rEFInd Boot Manager">
<input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
-<input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
-<img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
+<input type="image" src="donate.png" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
</form>
</td>
<input type="hidden" name="amount" value="5.00">
<input type="hidden" name="item_name" value="rEFInd Boot Manager">
<input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
-<input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
-<img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
+<input type="image" src="donate.png" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
</form>
</td>
<input type="hidden" name="amount" value="10.00">
<input type="hidden" name="item_name" value="rEFInd Boot Manager">
<input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
-<input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
-<img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
+<input type="image" src="donate.png" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
</form>
</td>
<input type="hidden" name="amount" value="20.00">
<input type="hidden" name="item_name" value="rEFInd Boot Manager">
<input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
-<input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
-<img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
+<input type="image" src="donate.png" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
</form>
</td>
<input type="hidden" name="currency_code" value="USD">
<input type="hidden" name="item_name" value="rEFInd Boot Manager">
<input type="hidden" name="bn" value="PP-DonationsBF:btn_donate_LG.gif:NonHostedGuest">
-<input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
-<img alt="Donate with PayPal" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
+<input type="image" src="donate.png" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
</form>
</td></tr>
</table>
<li class="tight"><a href="#installsh">Installing rEFInd Using <tt>refind-install</tt> under Linux or Mac OS X</a>
- <ul class="tight">
-
- <li class="tight"><a href="#quickstart">Quick <tt>refind-install</tt> Instructions</a></li>
-
- <li class="tight"><a href="#extra_installsh">Extra <tt>refind-install</tt> Instructions</a></li>
-
- </ul></li>
-
<li class="tight"><a href="#manual">Installing rEFInd Manually</a>
<ul>
<p>I provide RPM and Debian package files for rEFInd; and starting with version 0.8.1, I'm maintaining an Ubuntu PPA for rEFInd. If you have a working RPM-based or Debian-based Linux installation that boots in EFI mode, using one of these files is likely to be the easiest way to install rEFInd: You need only download the file and issue an appropriate installation command. In some cases, double-clicking the package in your file manager will install it. If that doesn't work, a command like the following will install the RPM on an RPM-based system:</p>
-<pre class="listing"># <tt class="userinput">rpm -Uvh refind-0.9.2-1.x86_64.rpm</tt></pre>
+<pre class="listing"># <tt class="userinput">rpm -Uvh refind-0.10.0-1.x86_64.rpm</tt></pre>
<p>On a Debian-based system, the equivalent command is:</p>
-<pre class="listing"># <tt class="userinput">dpkg -i refind_0.9.2-1_amd64.deb</tt></pre>
+<pre class="listing"># <tt class="userinput">dpkg -i refind_0.10.0-1_amd64.deb</tt></pre>
<p>Either command produces output similar to that described for <a href="#installsh">using the <tt>refind-install</tt> script,</a> so you can check it for error messages and other signs of trouble. The package file installs rEFInd and registers it with the EFI to be the default boot loader. The script that runs as part of the installation process tries to determine if you're using Secure Boot, and if so it will try to configure rEFInd to launch using shim; however, this won't work correctly on all systems. Ubuntu 12.10 users who are booting with Secure Boot active should be wary, since the resulting installation will probably try to use Ubuntu's version of shim, which won't work correctly with rEFInd. The shim program provided with more recent versions of Ubuntu should work correctly.</p>
<a name="installsh">
<h2>Installing rEFInd Using <tt>refind-install</tt> under Linux or Mac OS X</h2>
-<p class="sidebar"><b>Warning:</b> If you're using a Macintosh, you should run <tt>refind-install</tt> from Mac OS X rather than from Linux. If run from Linux, rEFInd is unlikely to be fully installed. The reason is that Apple uses non-standard methods to enable a boot loader, and the Linux functions in <tt>refind-install</tt> assume standard EFI installation methods.</p>
+<p class="sidebar"><b>Note:</b> If you're using a Macintosh, it's best to install rEFInd from OS X, if possible. In the past, the Mac's firmware was quirky enough that the Linux tools didn't always work reliably. The matter seems to have improved with recent versions of Linux tools, but I can't guarantee success if you use Linux for this task. There is one significant issue with OS X 10.11, though (see the next Warning sidebar).</p>
<p>If you're using Linux or Mac OS X, the easiest way to install rEFInd is to use the <tt>refind-install</tt> script. This script automatically copies rEFInd's files to your ESP or other target location and makes changes to your firmware's NVRAM settings so that rEFInd will start the next time you boot. If you've booted to OS X or in non-Secure-Boot EFI mode to Linux on a UEFI-based PC, <tt>refind-install</tt> will probably do the right thing, so you can get by with the quick instructions. If your setup is unusual, if your computer uses Secure Boot, or if you want to create a USB flash drive with rEFInd on it, you should read the <a href="#extra_installsh">extra instructions</a> for this utility.</p>
-<a name="quickstart">
-<h3>Quick <tt>refind-install</tt> Instructions</h3>
-</quickstart>
-
-<p class="sidebar"><b>Warning:</b> I've received reports that the OS X 10.11 ("El Capitan") beta has made changes to the OS that break the rEFInd installation procedure. This problem has been publicly reported as a bug in <tt>bless</tt>—see, for instance, <a href="http://www.openradar.me/22397509">here</a> and <a href="http://www.openradar.me/22170141">here.</a> It seems to be related to a new feature called System Integrity Protection. If possible, I recommend using OS X 10.10 ("Yosemite") or earlier to install rEFInd until this issue is resolved. It's reportedly possible to disable this feature by booting to recovery mode (by holding down Alt while booting) and typing <tt class="userinput">csrutil disable</tt> in a Terminal. After installing rEFInd, you can re-enable this feature by repeating the process, but typing <tt class="userinput">csrutil enable</tt>.</p>
+<p class="sidebar"><b>Warning:</b> OS X 10.11 ("El Capitan") implements a new feature called System Integrity Protection (SIP; aka "rootless" or "CSR"). When enabled, SIP prevents the final step of rEFInd installation—registering the boot loader with the firmware. Thus, to install rEFInd, you must either disable SIP or perform the installation from something other than your regular OS X installation. The <a href="sip.html">rEFInd and System Integrity Protection</a> page of this document describes the options.</p>
<p>By default, the <tt>refind-install</tt> script installs rEFInd to your disk's ESP. Under Mac OS X, you can instead install rEFInd to your current OS X boot partition by passing the script the <tt>--notesp</tt> option, or to a non-boot HFS+ partition by using the <tt>--ownhfs <tt class="variable">devicefile</tt></tt> option. Under either OS, you can install to something other than the currently-running OS by using the <tt>--root <tt class="variable">/mountpoint</tt></tt> option. (See <a href="#table1">Table 1</a> for details.)</p>
<p>Note that the change to an ESP location for rEFInd with version 0.8.4 means that, if you upgrade rEFInd from an earlier version, you may notice a rEFInd boot option in the rEFInd menu. This option will boot the old version of rEFInd (or the new one, if something went wrong and the old version continues to boot). You can rid yourself of the unwanted boot menu by deleting the old files or by using <tt>dont_scan_dirs</tt> or <tt>dont_scan_files</tt> in <tt>refind.conf</tt>. Before you do this, you should use rEFInd to identify the unwanted files—the filename and volume identifier appear under the icons when you highlight the option. You can then locate and delete them from within OS X. Before you delete the old files, though, you may want to copy over any changes you've made to the rEFInd configuration, icons, and other support files.</p>
-<a name="extra_installsh">
-<h3>Extra <tt>refind-install</tt> Instructions</h3>
-</a>
-
-<p>Some details that can affect how the script runs include the following:</p>
-
-<ul>
-
-<li>If you run the script as an ordinary user, it attempts to acquire
- <tt>root</tt> privileges by using the <tt>sudo</tt> command. This works
- on Mac OS X and some Linux installations (such as under Ubuntu or if
- you've added yourself to the <tt>sudo</tt> users list), but on some
- Linux installations this will fail. On such systems, you should run
- <tt>refind-install</tt> as <tt>root</tt>.</li>
-
-<li>Under OS X, you can run the script with a mouse by opening a Terminal
- session and then dragging-and-dropping the <tt>refind-install</tt> file to
- the Terminal window. You'll need to press the Return or Enter key to
- run the script.</li>
-
-<li>If you're using OS X 10.7's Whole Disk Encryption (WDE) feature, or the
- loogical volumes feature in OS X 10.10, you <i>must</i> install rEFInd
- to the ESP or to a separate HFS+ partition. The default in rEFInd 0.8.4
- and later is to install to the ESP. If you prefer to use a separate
- HFS+ volume, the <tt>--ownhfs <tt
- class="variable">device-file</tt></tt> option to <tt>refind-install</tt> is
- required.</li>
-
-<li>If you're <i>not</i> using WDE or logical volumes, you can install
- rEFInd to the OS X root (<tt>/</tt>) partition by using the
- <tt>--notesp</tt> option to <tt>refind-install</tt>. Using this option is
- recommended when upgrading from a working rEFInd installation in this
- location.</li>
-
-<li>If you're replacing rEFIt with rEFInd on a Mac, there's a chance that
- <tt>refind-install</tt> will warn you about the presence of a program
- called <tt>/Library/StartupItems/rEFItBlesser</tt> and ask if you want
- to delete it. This program is designed to keep rEFIt set as the boot
- manager by automatically re-blessing it if the default boot manager
- changes. This is obviously undesirable if you install rEFInd as your
- primary boot manager, so it's generally best to remove this program. If
- you prefer to keep your options open, you can answer <tt
- class="userinput">N</tt> when <tt>refind-install</tt> asks if you want to
- delete rEFItBlesser, and instead manually copy it elsewhere. If you
- subsequently decide to go back to using rEFIt as your primary boot
- manager, you can restore rEFItBlesser to its place.</li>
-
-<li>If you're using OS X and an Advanced Format disk, heed the warning that
- <tt>refind-install</tt> displays and <i><b>do not</b></i> use <tt>bless
- --info</tt> to check your installation status; this combination has
- been reported to cause disk corruption on some Macs!</li>
-
-<li>If you intend to boot BIOS-based OSes on a UEFI-based PC, you
- <i>must</i> edit the <tt>refind.conf</tt> file's <tt>scanfor</tt> line
- to enable the relevant searches. This is <i>not</i> necessary on Macs,
- though; because of the popularity of dual boots with Windows on Macs,
- the BIOS/legacy scans are enabled by default on Macs.</li>
-
-<li>On Linux, <tt>refind-install</tt> checks the filesystem type of the
- <tt>/boot</tt> directory and, if a matching filesystem driver is
- available, installs it. Note that the "<tt>/boot</tt> directory" may be
- on a separate partition or it may be part of your root (<tt>/</tt>)
- filesystem, in which case the driver for your root filesystem is
- installed. This feature is unlikely to work properly from an emergency
- system, although it might if you have a separate <tt>/boot</tt>
- partition and if you mount that partition at <tt>/boot</tt> in your
- emergency system, and the ESP at <tt>/boot/efi</tt>.</li>
-
-<li>On OS X, <tt>refind-install</tt> checks your partition tables for signs of
- a Linux installation. If such a sign is found, the script installs the
- EFI filesystem driver for the Linux ext4 filesystem. This will enable
- rEFInd to read your Linux kernel <i>if</i> it's on an ext2, ext3, or
- ext4 filesystem. Note that some configurations will require a
- <tt>/boot/refind_linux.conf</tt> file, which can be reliably generated
- only under Linux. (The <tt>mkrlconf</tt> script that comes with
- rEFInd will do this job once you've booted Linux.) In the meantime, you
- can launch GRUB from rEFInd or press F2 or Insert twice after
- highlighting the Linux option in rEFInd. This will enable you to enter
- a <tt>root=/dev/<tt class="variable">whatever</tt></tt> specification,
- where <tt>/dev/<tt class="variable">whatever</tt></tt> is the device
- identifier of your Linux root (<tt>/</tt>) filesystem.
-
-<li>If you run <tt>refind-install</tt> on Linux and if
- <tt>/boot/refind_linux.conf</tt> doesn't already exist,
- <tt>refind-install</tt> creates this file and populates it with a few
- sample entries. If <tt>/boot</tt> is on a FAT partition (or HFS+ on a
- Mac), or if it's on an ext2fs, ext3fs, ext4fs, ReiserFS, or HFS+
- partition and you install an appropriate driver, the
- result is that rEFInd will detect your kernel and will probably boot it
- correctly. Some systems will require manual tweaking to
- <tt>refind_linux.conf</tt>, though—for instance, to add
- <tt>dolvm</tt> to the boot options on Gentoo systems that use LVM.</li>
-
-<li>If you pass the <tt>--shim</tt> option to the script (along with a
- filename for a shim binary), the script sets up for a Secure Boot
- configuration via shim. By default, this causes the rEFInd binary to be
- renamed as <tt>grubx64.efi</tt>. Recent versions of shim support
- passing the name of the follow-on program to shim via a parameter,
- though. If you want to use this feature, you can pass the
- <tt>--keepname</tt> option to <tt>refind-install</tt>.</li>
-
-</ul>
-
-<p>In addition to these quirks, you should be aware of some options that <tt>refind-install</tt> supports to enable you to customize your installation in various ways. The syntax for <tt>refind-install</tt> is as follows:</p>
-
-<pre class="listing">
-refind-install [--notesp | --usedefault <tt class="variable">device-file</tt> | --root <tt class="variable">mount-point</tt> | \
- --ownhfs <tt class="variable">device-file</tt> ] [--keepname ] \
- [--nodrivers | --alldrivers] [--shim <tt class="variable">shim-filename</tt>] [--localkeys] [--yes]
-</pre>
-
-<p>The details of the options are summarized in <a href="#table1">Table 1.</a> Broadly speaking, they come in four classes: installation location options (<tt>--notesp</tt>, <tt>--usedefault</tt>, and <tt>--root</tt>), driver options (<tt>--nodrivers</tt> and <tt>--alldrivers</tt>), Secure Boot options (<tt>--shim</tt> and <tt>--localkeys</tt>), and a user input option (<tt>--yes</tt>). Using some of these options in unusual conditions can generate warnings and prompts to confirm your actions. In particular, using <tt>--shim</tt> or <tt>--localkeys</tt> when you're <i>not</i> booted in Secure Boot mode, or failing to use <tt>--shim</tt> when you <i>are</i> booted in Secure Boot mode, will generate a query and a request to confirm your installation. Consult the <a href="secureboot.html">Managing Secure Boot</a> page for more on this topic.</p>
-
-<table border="1" cellpadding="1" cellspacing="2" summary="Table 1: Options to <tt>refind-install</tt>"><a name="table1"><caption><b>Table 1: Options to <tt>refind-install</tt></b></caption></a>
-<tr>
- <th>Option</th>
- <th>Explanation</th>
-</tr>
-<tr>
- <td><tt>--notesp</tt></td>
- <td>This option, which is valid only under OS X, tells <tt>refind-install</tt> to install rEFInd to the OS X root partition rather than to the ESP. This behavior was the default in rEFInd 0.8.3 and earlier, so you may want to use it when upgrading installations of that version, unless you used <tt>--esp</tt> (which is now the default behavior, although the <tt>--esp</tt> option no longer exists) or <tt>--ownhfs</tt>. You may also want to use <tt>--notesp</tt> on new installations if you're sure you're <i>not</i> using whole-disk encryption or logical volumes.</td>
-</tr>
-<tr>
- <td><tt>--usedefault <tt class="variable">device-file</tt></tt></td>
- <td>You can install rEFInd to a disk using the default/fallback filename of <tt>EFI/BOOT/bootx64.efi</tt> (and <tt>EFI/BOOT/bootia32.efi</tt>, if the 32-bit build is available) using this option. The <tt class="variable">device-file</tt> should be an <i>unmounted</i> ESP, or at least a FAT partition, as in <tt>--usedefault /dev/sdc1</tt>. Your computer's NVRAM entries will <i>not</i> be modified when installing in this way. The intent is that you can create a bootable USB flash drive or install rEFInd on a computer that tends to "forget" its NVRAM settings with this option. This option is mutually exclusive with <tt>--notesp</tt> and <tt>--root</tt>.</td>
-</tr>
-<tr>
- <td><tt>--ownhfs <tt class="variable">device-file</tt></tt></td>
- <td>This option should be used <i>only</i> under OS X. It's used to install rEFInd to an HFS+ volume <i>other than</i> a standard Mac boot volume. The result should be that rEFInd will show up in the Mac's own boot manager. More importantly, suspend-to-RAM operations may work correctly. Note that this option requires an HFS+ volume that is <i>not</i> currently an OS X boot volume. This can be a data volume or a dedicated rEFInd partition. The ESP might also work, if it's converted to use HFS+.</td>
-</tr>
-<tr>
- <td><tt>--root <tt class="variable">/mount-point</tt></tt></td>
- <td>This option is intended to help install rEFInd from a "live CD" or other emergency system. To use it, you should mount your regular installation at <tt class="variable">/mount-point</tt>, including your <tt>/boot</tt> directory (if it's separate) at <tt class="variable">/mount-point</tt><tt>/boot</tt> and (on Linux) your ESP at that location or at <tt class="variable">/mount-point</tt><tt>/boot/efi</tt>. The <tt>refind-install</tt> script then installs rEFInd to the appropriate location—on Linux, <tt class="variable">/mount-point</tt><tt>/boot/EFI/refind</tt> or <tt class="variable">/mount-point</tt><tt>/boot/efi/EFI/refind</tt>, depending on where you've mounted your ESP. Under OS X, this option is only useful in conjunction with <tt>--notesp</tt>, in which case rEFInd will install to <tt class="variable">/mount-point</tt><tt>/EFI/refind</tt>. The script also adds an entry to your NVRAM for rEFInd at this location. You cannot use this option with <tt>--usedefault</tt>. Note that this option is <i>not</i> needed when doing a dual-boot Linux/OS X installation; just install normally in OS X.</td>
-</tr>
-<tr>
- <td><tt>--nodrivers</tt></td>
- <td>Ordinarily <tt>refind-install</tt> attempts to install the driver required to read <tt>/boot</tt> on Linux. This attempt works only if you're using ext2fs, ext3fs, ext4fs, or ReiserFS on the relevant partition. If you want to forego this driver installation, pass the <tt>--nodrivers</tt> option. This option is the implicit when you use <tt>--usedefault</tt>.</td>
-</tr>
-<tr>
- <td><tt>--alldrivers</tt></td>
- <td>When you specify this option, <tt>refind-install</tt> copies <i>all</i> the driver files for your architecture. You may want to remove unused driver files after you use this option, especially if your computer uses Secure Boot. Note that some computers hang or fail to work with any drivers if you use this option, so use it with caution.</td>
-</tr>
-<tr>
- <td><tt>--shim <tt class="variable">shim-filename</tt></tt> or <tt>--preloader <tt class="variable">preloader-filename</tt></tt></td>
- <td>If you pass this option to <tt>refind-install</tt>, the script will copy the specified shim program file to the target directory, copy the <tt>MokManager.efi</tt> file from the shim program file's directory to the target directory, copy the 64-bit version of rEFInd as <tt>grubx64.efi</tt>, and register shim with the firmware. (If you also specify <tt>--usedefault</tt>, the NVRAM registration is skipped. If you also use <tt>--keepname</tt>, the renaming to <tt>grubx64.efi</tt> is skipped.) When the target file is identified as PreLoader, much the same thing happens, but <tt>refind-install</tt> copies <tt>HashTool.efi</tt> instead of <tt>MokManager.efi</tt> and copies rEFInd as <tt>loader.efi</tt> rather than as <tt>grubx64.efi</tt>. The intent is to simplify rEFInd installation on a computer that uses Secure Boot; when so set up, rEFInd will boot in Secure Boot mode, with one caveat: The first time you boot, MokManager/HashTool will launch, and you must use it to locate and install a public key or register rEFInd as a trusted application. The rEFInd public key file will be located in the rEFInd directory's <tt>keys</tt> subdirectory under the name <tt>refind.cer</tt>. Note that I'm not providing a shim binary myself, but you can download one from <a href="http://www.codon.org.uk/~mjg59/shim-signed/">here.</a> Some distributions also provide their own shim programs, so can point to them—for instance, in <tt>/boot/efi/EFI/fedora/shim.efi</tt>.</td>
-</tr>
-<tr>
- <td><tt>--localkeys</tt></td>
- <td>This option tells <tt>refind-install</tt> to generate a new Machine Owner Key (MOK), store it in <tt>/etc/refind.d/keys</tt> as <tt>refind_local.*</tt>, and re-sign all the 64-bit rEFInd binaries with this key before installing them. This is the preferable way to install rEFInd in Secure Boot mode, since it means your binaries will be signed locally rather than with my own key, which is used to sign many other users' binaries; however, this method requires that both the <tt>openssl</tt> and <tt>sbsign</tt> binaries be installed. The former is readily available in most distributions' repositories, but the latter is not, so this option is not the default.</td>
-</tr>
-<tr>
- <td><tt>--keepname</tt></td>
- <td>This option is useful only in conjunction with <tt>--shim</tt>. It tells <tt>refind-install</tt> to keep rEFInd's regular filename (typically <tt>refind_x64.efi</tt>) when used with shim, rather than rename the binary to <tt>grubx64.efi</tt>. This change cuts down on the chance of confusion because of filename issues; however, this feature requires that shim be launched with a command-line parameter that points to the rEFInd binary under its real name. versions of shim prior to 0.7 do not properly support this feature. (Version 0.4 supports it but with a buggy interpretation of the follow-on loader specification.) If your NVRAM variables become corrupted or are forgotten, this feature may make rEFInd harder to launch. This option is incompatible with <tt>--usedefault</tt> and is unavailable when run under OS X or without the <tt>--shim</tt> option. If the script discovers an existing rEFInd installation under <tt>EFI/BOOT</tt> or <tt>EFI/Microsoft/Boot</tt> and no other rEFInd installation when this option is used, it will abort.</td>
-</tr>
-<tr>
- <td><tt>--yes</tt></td>
- <td>This option causes the script to assume a <tt>Y</tt> input to every yes/no prompt that can be generated under certain conditions, such as if you specify <tt>--shim</tt> but <tt>refind-install</tt> detects no evidence of a Secure Boot installation. This option is intended mainly for use by scripts such as those that might be used as part of an installation via an RPM or Debian package.</td>
-</tr>
-</table>
-
-<p>After you run <tt>refind-install</tt>, you should peruse the script's output to ensure that everything looks OK. <tt>refind-install</tt> displays error messages when it encounters errors, such as if the ESP is mounted read-only or if you run out of disk space. You may need to correct such problems manually and re-run the script. In some cases you may need to fall back on manual installation, which gives you better control over details such as which partition to use for installation.</p>
+<p>The <tt>refind-install</tt> script supports a number of options that can affect how it operates. For information on these options, consult the script's man page: Type <tt class="userinput">man refind-install</tt> if you installed rEFInd via an RPM or Debian package; or read it in <a href="refind-install.html">HTML form.</a></p>
<a name="manual">
<h2>Installing rEFInd Manually</h2>
/dev/sda1 191284 16604 174681 9% /boot/efi
</pre>
-<p class="sidebar"><b>Warning:</b> If you're running Linux on a Mac, I recommend you install rEFInd under OS X. The Mac's boot process deviates a bit from EFI standards, so you'll probably have to use a tool called <tt>bless</tt> under Mac OS to do the job. Alternatively, there's a new Linux program, <tt>hfs-bless</tt>, part of the <a href="http://www.codon.org.uk/~mjg59/mactel-boot/"><tt>mactel-boot</tt></a> RPM package or as part of the <a href="https://launchpad.net/~detly/+archive/ubuntu/mactel-utils">mactel-utils PPA for Ubuntu</a>, that's supposed to work with <tt>efibootmgr</tt> to make a Mac HFS partition bootable. I've not yet tried it, though. There are also reports that the <tt>efibootmgr</tt> tool used under Linux can corrupt some Macs' firmware. Although I've seen some vague suggestions that this problem has been fixed under 3.<i>x</i> kernels, I haven't tested this claim.</p>
+<p class="sidebar"><b>Note:</b> If you're running Linux on a Mac, I recommend you install rEFInd under OS X. The Mac's boot process deviates a bit from EFI standards, and older versions of <tt>efibootmgr</tt> didn't always work properly on Macs. This problem seems to have gone away with more recent versions of <tt>efibootmgr</tt>, but using OS X may still be more reliable. On the other hand, Apple's new (as of OS X 10.11) System Integrity Protection (SIP) feature blocks the use of <tt>bless</tt> under OS X and so prevents rEFInd installation. The <a href="sip.html">rEFInd and System Integrity Protection</a> page of this document covers how to overcome SIP and install rEFInd. One of these methods is to do the job from Linux.</p>
<p>This example shows that <tt>/dev/sda1</tt> is mounted at <tt>/boot/efi</tt>, which is a typical configuration. (The ESP can be on another disk or partition, but <tt>/dev/sda1</tt> is the most common place for an ESP.) If your output shows <tt>/boot</tt> or <tt>/</tt> under the <tt>Mounted on</tt> column, then your ESP isn't mounted. (An exception is if you're mounting the ESP at <tt>/boot</tt>. This is an unusual configuration. If you're using it, you can proceed, making suitable adjustments to subsequent commands.) If you get a <tt>df: `/boot/efi': No such file or directory</tt> error message, then the <tt>/boot/efi</tt> directory doesn't even exist. In such cases, you may need to jump through some extra hoops, as described on my <a href="http://www.rodsbooks.com/efi-bootloaders/installation.html">EFI Boot Loader Installation</a> page.</p>
<h3>Installing rEFInd Manually Using Mac OS X</h3>
</a>
-<p class="sidebar"><b>Warning:</b> I've received reports that the OS X 10.11 ("El Capitan") beta has made changes to the OS that break the rEFInd installation procedure. This problem has been publicly reported as a bug in <tt>bless</tt>—see, for instance, <a href="http://www.openradar.me/22397509">here</a> and <a href="http://www.openradar.me/22170141">here.</a> It seems to be related to a new feature called System Integrity Protection. If possible, I recommend using OS X 10.10 ("Yosemite") or earlier to install rEFInd until this issue is resolved. It's reportedly possible to disable this feature by booting to recovery mode (by holding down Alt while booting) and typing <tt class="userinput">csrutil disable</tt> in a Terminal. After installing rEFInd, you can re-enable this feature by repeating the process, but typing <tt class="userinput">csrutil enable</tt>.</p>
+<p class="sidebar"><b>Warning:</b> OS X 10.11 ("El Capitan") implements a new feature called System Integrity Protection (SIP; aka "rootless" or "CSR"). When enabled, SIP prevents the final step of rEFInd installation—registering the boot loader with the firmware. Thus, to install rEFInd, you must either disable SIP or perform the installation from something other than your regular OS X installation. The <a href="sip.html">rEFInd and System Integrity Protection</a> page of this document describes the options. If you're an advanced enough user to be considering a manual rEFInd installation procedure, doing the job from the Recovery HD environment may be your best option.</p>
<p>Before installing rEFInd on a Mac, you must determine whether it uses a 32-bit or 64-bit EFI implementation. Most Intel-based Macs have 64-bit EFIs, so you should use the <tt>refind_x64.efi</tt> file with them; but very early Intel-based Macs have 32-bit EFIs (and sometimes 32-bit CPUs), which require the <tt>refind_ia32.efi</tt> file. You can determine whether your Mac needs the <i>x</i>86-64 or IA32 build by typing the following command in a Mac Terminal window:</p>
<li>Open a Terminal window in which you'll type the following
commands.</li>
-<li>If you want to install rEFInd on your ESP, you must first mount it. You
- can do this by typing <b><tt>mkdir /Volumes/esp</tt></b> followed by
- <b><tt>sudo mount -t msdos /dev/disk0s1 /Volumes/esp</tt></b>. Note
- that you may need to change <tt>/dev/disk0s1</tt> to something else if
- your ESP is at an unusual location. Type <tt class="userinput">diskutil
- list</tt> or use a tool such as my <a
- href="http://www.rodsbooks.com/gdisk/">GPT fdisk (<tt>gdisk</tt>)</a>
- to examine your partition table to find your ESP if necessary.</li>
-
-<li>Type <b><tt>sudo mkdir -p /Volumes/esp/efi/refind</tt></b> to create a
+<li>If you want to install rEFInd on your ESP, you must first mount it. The
+ easy way to do this is to use the <tt>mountesp</tt> script that comes
+ with rEFInd. When you run it, the script should tell you where the ESP
+ was mounted. You can do the job manually by typing <b><tt>mkdir
+ /Volumes/ESP</tt></b> followed by <b><tt>sudo mount -t msdos
+ /dev/disk0s1 /Volumes/ESP</tt></b>. Note that you may need to change
+ <tt>/dev/disk0s1</tt> to something else if your ESP is at an unusual
+ location. Type <tt class="userinput">diskutil list</tt> or use a tool
+ such as my <a href="http://www.rodsbooks.com/gdisk/">GPT fdisk
+ (<tt>gdisk</tt>)</a> to examine your partition table to find your ESP
+ if necessary.</li>
+
+<li>Type <b><tt>sudo mkdir -p /Volumes/ESP/efi/refind</tt></b> to create a
suitable directory for rEFInd. If you want to place rEFInd on the OS X
root partition, you should adjust the pathname appropriately, as in
<tt>/efi/refind</tt>. Alternatively, you can use the Finder to create
<li>Copy the files in the <tt>refind</tt> subdirectory of the rEFInd binary
package to the like-named directory you've just created. You can do
this in the Finder or by typing <b><tt>sudo cp -r refind/*
- /Volumes/esp/efi/refind/</tt></b> in your Terminal window after
+ /Volumes/ESP/efi/refind/</tt></b> in your Terminal window after
changing into the rEFInd package's main directory.</li>
<li>Remove the file for the version of rEFInd you're not using, as in
<b><tt>sudo rm Volumes/esp/efi/refind/refind_ia32.efi</tt></b> on a Mac
with a 64-bit EFI or <b><tt>sudo rm
- /Volumes/esp/efi/refind/refind_x64.efi</tt></b> on a Mac with a 32-bit
+ /Volumes/ESP/efi/refind/refind_x64.efi</tt></b> on a Mac with a 32-bit
EFI.</li>
<li>Optionally, remove the drivers directory for the architecture you're
- not using—<tt>/Volumes/esp/efi/refind/drivers_ia32</tt> or
- <tt>/Volumes/esp/efi/refind/drivers_x64</tt>, as appropriate. You may
+ not using—<tt>/Volumes/ESP/efi/refind/drivers_ia32</tt> or
+ <tt>/Volumes/ESP/efi/refind/drivers_x64</tt>, as appropriate. You may
also want to remove some or all of the drivers for the architecture you
are using; if you don't need them, they'll slow down the start process.
See the <a href="drivers.html">page on drivers</a> for more on this
HFS+ driver provided with rEFInd is useless on Macs.</li>
<li>If this is your first installation, type <b><tt>sudo mv
- /Volumes/esp/efi/refind/refind.conf-sample
- /Volumes/esp/efi/refind/refind.conf</tt></b> (adjusting the path as
+ /Volumes/ESP/efi/refind/refind.conf-sample
+ /Volumes/ESP/efi/refind/refind.conf</tt></b> (adjusting the path as
necessary) to rename the sample configuration file so that it will
serve as a real configuration file. (Again, you can do this with the
Finder, if you prefer.)</li>
<li>"Bless" rEFInd by typing one of the following two commands:
<ul>
<li>If you're installing rEFInd on the ESP, type <tt
- class="userinput">sudo bless --mount /Volumes/esp --setBoot --file
- /Volumes/esp/efi/refind/refind_x64.efi --shortform</tt>, adjusting
+ class="userinput">sudo bless --mount /Volumes/ESP --setBoot --file
+ /Volumes/ESP/efi/refind/refind_x64.efi --shortform</tt>, adjusting
the mount point and exact path to the file as appropriate for your
installation.</li>
<li>If you're installing rEFInd to an ordinary HFS+ volume, type <tt
necessary if you're placing rEFInd somewhere else or using the
32-bit version.)</li>
</ul>
- As per the Warning earlier, <i>do not</i> use <tt>bless</tt>'s
- <tt>--info</tt> option to try to confirm the change to the boot status
- unless you're certain you do <i>not</i> have an Advanced Format hard
- disk.</li>
+ This is the step that's likely to fail if your system is booted
+ with SIP active.</li>
<li>If you don't want to reboot immediately after installing rEFInd, you
may optionally unmount the ESP by typing <tt class="userinput">sudo
umount /dev/disk0s1</tt> or <tt class="userinput">sudo umount
- /Volumes/esp</tt>. This step isn't strictly required, but if you want
+ /Volumes/ESP</tt>. This step isn't strictly required, but if you want
to keep the ESP out of your directory tree, it can be useful.</li>
</ol>
<h3>Using the <tt>--shortform</tt> Option</h3>
</a>
-<p>Prior to version 0.8.5, these instructions and the <tt>refind-install</tt> script omitted the <tt>--shortform</tt> option from the <tt>bless</tt> command when installing rEFInd to the ESP. An rEFInd user, however, discovered that using the option eliminated the 30-second delay, so it is now the default with 0.8.5's <tt>refind-install</tt>, and is specified in the instructions. If you installed rEFInd 0.8.4 or earlier, you may want to re-install or re-<tt>bless</tt> rEFInd using this option.</p>
+<p>Prior to version 0.8.5, these instructions and the <tt>refind-install</tt> script omitted the <tt>--shortform</tt> option from the <tt>bless</tt> command when installing rEFInd to the ESP. A rEFInd user, however, discovered that using the option eliminated the 30-second delay, so it is now the default with 0.8.5's <tt>refind-install</tt>, and is specified in the instructions. If you installed rEFInd 0.8.4 or earlier, you may want to re-install or re-<tt>bless</tt> rEFInd using this option.</p>
<p>There is one caveat, though: The <tt>man</tt> page for <tt>bless</tt> notes that <tt>--shortform</tt> notes that its use can come "at the expense of boot time performance." Thus, it's not clear to me that this option might not actually <i>create</i> problems on some computers. (It's eliminated the boot delay on my 2014 MacBook Air and has no detrimental effect on an old 32-bit Mac Mini that's never had a boot delay problem, though.) Thus, if you have problems with rEFInd 0.8.5 or later, you might try running <tt>bless</tt>, as described in <a href="#osx">Installing rEFInd Manually Using OS X's</a> step 8, but <i>omit</i> the <tt>--shortform</tt> option.</p>
<li>If necessary, mount the ESP or rEFInd-specific HFS+ volume, as
described in <a href="#osx">Installing rEFInd Manually Using Mac OS
- X.</a></li>
+ X.</a> (The <tt>mountesp</tt> script that comes with rEFInd will handle
+ this task.)</li>
<li>Verify that rEFInd is installed in the directory noted in step #1. If a
<tt>refind.conf</tt> file is present, rEFInd is almost certainly
<tt>bootx64.efi</tt>, <tt>boot.efi</tt>, or conceivably something else.
You may need to use <tt>sudo rm</tt> at the command line to accomplish
this task, as in <tt class="userinput">sudo rm -r
- /Volumes/esp/EFI/refind</tt>.</li>
+ /Volumes/ESP/EFI/refind</tt>.</li>
</ol>
BootOrder: 0007
Boot0007* CD/DVD Drive</pre>
-<p class="sidebar"><b>Warning:</b> As noted earlier, <tt>efibootmgr</tt> has been linked to firmware corruption on some Macs, at least with pre-3.3.0 Linux kernels. Therefore, I don't recommend using <tt>efibootmgr</tt> on Macs.</p>
-
<p>This example shows use of <tt>efibootmgr</tt>'s <tt>--verbose</tt> (<tt>-v</tt>) option to display boot programs so as to identify which one is rEFInd, followed by <tt>--delete-bootnum</tt> (<tt>-B</tt>) to delete a boot program and <tt>--bootnum</tt> (<tt>-b</tt>) to identify which one to delete. Of course, in this example there's not much else left, so you'd presumably want to install another boot program at this point! If you already have another one installed, you may want to check the <tt>BootOrder</tt> line to determine which one will take precedence when you reboot. If you don't like what it shows, you can adjust it with the <tt>--bootorder</tt> (<tt>-o</tt>) option; consult <tt>efibootmgr</tt>'s <tt>man</tt> page for details.</p>
<p>If you're not using Linux, you may be able to find a utility that serves