+NOTE: If you want to boot an OS via BIOS emulation (such as Windows or some
+Linux installations), you *MUST* edit the ///EFI/refind/refind.conf
+file's 'scanfor' line to include the 'hdbios' option, and perhaps
+'biosexternal' and 'cd', as well.
+
+
+Installation has completed successfully.</pre>
+
+<p>In either case, the details of the output differ depending on your existing configuration and how you ran the program. 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 "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>
+ 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 file called
+ <tt>/Library/StartupItems/rEFItBlesser</tt> and ask if you want to
+ delete the file. This file 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 file. 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, such as most Windows
+ installations and some Linux installations, you <i>must</i> edit the
+ <tt>refind.conf</tt> file, as noted near the end of the installation
+ script's output. (Note that rEFInd can only boot such OSes on Macs at
+ the moment.)</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>