-<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, 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>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>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 [--esp | --usedefault <tt class="variable">device-file</tt> | --root <tt class="variable">mount-point</tt> ] \
- [--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>--esp</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>