+# <tt class="userinput">./install.sh</tt>
+Installing rEFInd on Linux....
+ESP was found at /boot/efi using vfat
+Installing driver for ext4 (ext4_x64.efi)
+Copied rEFInd binary files
+
+Copying sample configuration file as refind.conf; edit this file to configure
+rEFInd.
+
+
+Installation has completed successfully.</pre>
+
+<p>The output under OS X is a bit different:</p>
+
+<pre class="listing">
+$ <tt class="userinput">./install.sh</tt>
+Not running as root; attempting to elevate privileges via sudo....
+Password:
+Installing rEFInd on OS X....
+Installing rEFInd to the partition mounted at /Volumes/ESP
+Found suspected Linux partition(s); installing ext4fs driver.
+Installing driver for ext4 (ext4_ia32.efi)
+Copied rEFInd binary files
+
+Copying sample configuration file as refind.conf; edit this file to configure
+rEFInd.
+
+
+WARNING: If you have an Advanced Format disk, *DO NOT* attempt to check the
+bless status with 'bless --info', since this is known to cause disk corruption
+on some systems!!
+
+
+Installation has completed successfully.
+
+Unmounting install dir</pre>
+
+<p>In either case, the details of the output differ depending on your existing configuration and how you ran the program. Unless you see an obvious warning or error, you shouldn't be concerned about minor deviations from these examples. If you run into such a situation, or if you want to install in an unusual way, read on....</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>install.sh</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>install.sh</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>install.sh</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>install.sh</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>install.sh</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>install.sh</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>install.sh</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>install.sh</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>install.sh</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>install.sh</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.sh</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>install.sh</tt> on Linux and if
+ <tt>/boot/refind_linux.conf</tt> doesn't already exist,
+ <tt>install.sh</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>
+
+</ul>
+
+<p>In addition to these quirks, you should be aware of some options that <tt>install.sh</tt> supports to enable you to customize your installation in various ways. The syntax for <tt>install.sh</tt> is as follows:</p>
+
+<pre class="listing">
+install.sh [--notesp | --usedefault <tt class="variable">device-file</tt> | --root <tt class="variable">mount-point</tt> | \
+ --ownhfs <tt class="variable">device-file</tt> ] \
+ [--nodrivers | --alldrivers] [--shim <tt class="variable">shim-filename</tt>] [--localkeys] [--yes]