+<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>Under OS X, passing the <tt>--esp</tt> 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> will install rEFInd to the wrong partition if you
+ have multiple disks or if a disk has multiple ESPs. If you believe this
+ has happened, you 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
+ <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
+ forum thread</a> for a discussion of the topic.</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>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. This option also tells the script to <i>not</i> make
+ changes to the computer's NVRAM. 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">bash ./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>