href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-11/6/2012, referencing rEFInd 0.4.7</p>
+11/7/2012, referencing rEFInd 0.4.7</p>
<p>I'm a technical writer and consultant specializing in Linux technologies. 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>
the Terminal window. You'll need to press the Return or Enter key to
run the script.</li>
-<li>Under OS X, passing the "esp" option causes the script to install
+<li>Under OS X, passing the "--esp" option causes the script to install
rEFInd to the ESP. The script finds the first ESP that's identified by
the <tt>diskutil</tt> program and, if it's not already mounted, mounts
it to install rEFInd. Thus, it's conceivable that <tt>install.sh</tt>
may need to re-install manually.</li>
<li>If you're using OS X 10.7's Whole Disk Encryption (WDE) feature, you
- <i>must</i> install rEFInd to the ESP, so the <tt>esp</tt> option to
+ <i>must</i> install rEFInd to the ESP, so the <tt>--esp</tt> option to
<tt>install.sh</tt> is required. I'm still a little bit foggy about
what's required to boot the system once this is done; see <a
href="https://sourceforge.net/p/refind/discussion/general/thread/5c7d0195/">this
script's output. (Note that rEFInd can only boot such OSes on Macs at
the moment.)</li>
+<li>Under both Linux and OS X, you can add the <tt>--drivers</tt> option to
+ have <tt>install.sh</tt> install all the filesystem drivers along with
+ the main rEFInd program. (The default is to <i>not</i> install any
+ drivers.)</li>
+
+<li>Under both Linux and OS X, you can add the <tt>--usedefault <tt
+ class="variable">devicepath</tt></tt> option to install rEFInd to the
+ specified device as <tt>EFI/BOOT/bootx64.efi</tt> and
+ <tt>EFI/BOOT/bootia32.efi</tt>. The specified device must be a valid
+ FAT partition. The idea is that you can easily create a bootable USB
+ flash drive with this option: Create a proper FAT-formatted ESP on a
+ disk (say, <tt>/dev/sdd1</tt>) and then type <tt class="userinput">sh
+ ./install --usedefault /dev/sdd1</tt> to turn the disk into an
+ emergency disk. This option can also be used to install rEFInd to an
+ ESP using the <a href="#naming">alternative naming options</a>
+ described later. This latter usage will result in a bootable rEFInd
+ only if no other OS has already created an NVRAM variable pointing to
+ itself.</li>
+
</ul>
<p>In any event, you should peruse the script's output to ensure that everything looks OK. <tt>install.sh</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>
<li>Rename the configuration file by typing <tt><b>mv refind.conf-sample refind.conf</b></tt>. Consult the <a href="configfile.html">Editing the rEFInd Configuration File</a> page for information on how to adjust your options.</li>
+<p class="sidebar"><b>Weird:</b> I've received one report about a Lenovo computer that works only if rEFInd is installed using the name (<tt>-L</tt> parameter) <tt>Windows Boot Manager</tt> and the existing Windows boot loader, if present, is renamed.</p>
+
<a name="efibootmgr">
<li>On a UEFI-based system, type <tt><b>efibootmgr -c -l \\EFI\\refind\\refind_x64.efi -L rEFInd</b></tt> to add rEFInd to your EFI's list of available boot loaders, which it stores in NVRAM. (Adjust the path to the binary as required if you install somewhere else.) You may need to install this program on some systems; it's a standard part of most distributions' repositories.</li>
</a>
<p>When you reboot, rEFInd should come up. With any luck, it will detect your old boot loader as an option, if one was installed before.</p>
+<p>If your computer seems to insist on booting an EFI boot loader called <tt>EFI/Microsoft/BOOT/bootmgfw.efi</tt>, be aware that it might not actually be looking for that filename, but for a boot manager with the EFI description <tt>Microsoft Boot Manager</tt>. Changing the description of the "real" <tt>EFI/Microsoft/BOOT/bootmgfw.efi</tt> using <tt>efibootmgr</tt> and then giving rEFInd that description, even when rEFInd is installed in a more conventional location, may work. I've received a report that at least one Lenovo model has this peculiar affliction.</p>
+
<a name="upgrading">
<h2>Upgrading rEFInd</h2>
</a>