<p>This method requires that your <tt>/boot</tt> directory, whether it's on a separate partition or is a regular directory in your root (<tt>/</tt>) filesystem, be readable by the EFI. At the moment, all EFI implementations can read FAT and Macs can read HFS+. By using <a href="drivers.html">drivers,</a> you can make any EFI read HFS+, ISO-9660, ReiserFS, ext2fs, ext3fs, ext4fs, Btrfs, or other filesystems. Thus, if you use any of these filesystems on a regular partition (not an LVM or RAID configuration) that holds your kernels in <tt>/boot</tt>, you qualify for this easy method. The default partition layouts used by Ubuntu, Fedora, and many other distributions qualify, because they use one of these filesystems (usually ext4fs) in a normal partition or on a separate <tt>/boot</tt> partition. You must also have a 3.3.0 or later Linux kernel with EFI stub support, of course.</p>
-<p>If you installed rEFInd 0.6.0 or later with its <tt>install.sh</tt> script from your regular Linux installation, chances are everything's set up; you should be able to reboot and see your Linux kernels as boot options. If you installed manually, from OS X, or from an emergency system, though, you may need to do a couple of things manually:
+<p>If you installed rEFInd 0.6.0 or later with its <tt>refind-install</tt> (formerly <tt>install.sh</tt>) script from your regular Linux installation, chances are everything's set up; you should be able to reboot and see your Linux kernels as boot options. If you installed manually, from OS X, or from an emergency system, though, you may need to do a couple of things manually:
<ul>
Partition (ESP). You may need to create this subdirectory, too.</li>
<li>Create a <tt>refind_linux.conf</tt> file in your <tt>/boot</tt>
- directory. The <tt>mkrlconf.sh</tt> script that comes with rEFInd
+ directory. The <tt>mkrlconf</tt> script that comes with rEFInd
should do this job, or you can do it manually as described <a
href="#efistub">later.</a> Starting with version 0.6.12, rEFInd can
create minimal boot options from <tt>/etc/fstab</tt>, if <tt>/boot</tt>
<li>Copy the <tt>/boot/refind_linux.conf</tt> file to the same directory to
which you copied your kernel. If this file doesn't exist, create it by
- running (as <tt>root</tt>) the <tt>mkrlconf.sh</tt> script that came
+ running (as <tt>root</tt>) the <tt>mkrlconf</tt> script that came
with rEFInd. This step may not be strictly necessary if <tt>/boot</tt>
is an ordinary directory on your root (<tt>/</tt>) partition.</li>
<tt>/boot/refind_linux.conf</tt> and populate it with kernel options,
as described <a href="#refind_linux">later.</a> If this file doesn't
already exist, the easiest way to create it is to run the
- <tt>mkrlconf.sh</tt> script that comes with rEFInd 0.5.1 and
+ <tt>mkrlconf</tt> script that comes with rEFInd 0.5.1 and
later.</li>
<li>Check your <tt>refind.conf</tt> file (presumably in
each of which consists of a label followed by a series of kernel
options. The first line sets default options, and subsequent lines set
options that are accessible from the main menu tag's submenu screen. If
- you installed rEFInd with the <tt>install.sh</tt>
+ you installed rEFInd with the <tt>refind-install</tt>
script, that script created a sample <tt>refind_linux.conf</tt> file,
customized for your computer, in <tt>/boot</tt>. This file will work
without changes on many installations, but you may need to tweak it for
<p>Note that in this example, the default kernel (the one with the most recent time stamp) appears first on the list, with the labels specified in <tt>refind_linux.conf</tt>. Subsequent kernels (just one in this example) appear below it, with the same labels preceded by the kernel filename. If you were to set <tt>fold_linux_kernels false</tt>, each kernel would get its own entry on the main menu, and each one's submenu would enable options for launching it alone.</p>
-<p>To assist in initial configuration, rEFInd's <tt>install.sh</tt> script creates a sample <tt>refind_linux.conf</tt> file in <tt>/boot</tt>. This sample file defines three entries, the first two of which use the default GRUB options defined in <tt>/etc/default/grub</tt> and the last of which uses minimal options. The first entry boots normally and the second boots into single-user mode. If you want to create a new file, you can use the <tt>mkrlconf.sh</tt> script that comes with rEFInd. If you pass it the <tt>--force</tt> option, it will overwrite the existing <tt>/boot/refind_linux.conf</tt> file; otherwise it will create the file only if one doesn't already exist.</p>
+<p>To assist in initial configuration, rEFInd's <tt>refind-install</tt> script creates a sample <tt>refind_linux.conf</tt> file in <tt>/boot</tt>. This sample file defines three entries, the first two of which use the default GRUB options defined in <tt>/etc/default/grub</tt> and the last of which uses minimal options. The first entry boots normally and the second boots into single-user mode. If you want to create a new file, you can use the <tt>mkrlconf</tt> script that comes with rEFInd. If you pass it the <tt>--force</tt> option, it will overwrite the existing <tt>/boot/refind_linux.conf</tt> file; otherwise it will create the file only if one doesn't already exist.</p>
<p>From a user's perspective, the submenus defined in this way work just like submenus defined via the <tt>submenuentry</tt> options in <tt>refind.conf</tt>, or like the submenus that rEFInd creates automatically for Mac OS X or ELILO. There are, however, limitations in what you can accomplish with this method:</p>