Renamed support scripts: install.sh to refind-install, mvrefind.sh to

mvrefind, and mkrlconf.sh to mkrlconf.

diff --git a/BUILDING.txt b/BUILDING.txt
index f9d889ce7a52b15253454b8f85d801c4855f7598..4f6519372ae59aba73433e707327cb09abe0b302 100644 (file)
--- a/BUILDING.txt
+++ b/BUILDING.txt
@@ -230,16 +230,16 @@ Installing rEFInd
 =================
 
 With rEFInd compiled, you can install it. The easiest way to do this is
 =================
 
 With rEFInd compiled, you can install it. The easiest way to do this is

-with the install.sh script, which works on both Linux and Mac OS X.
+with the refind-install script, which works on both Linux and Mac OS X.

 Alternatively, you can type "make install" to install using this script.
 Note that this script copies files to the ESP and uses "efibootmgr" (on
 Linux) or "bless" (on OS X) to add rEFInd to the firmware's boot loader
 list. The docs/refind/installing.html file provides more details on this
 script and its use.
 
 Alternatively, you can type "make install" to install using this script.
 Note that this script copies files to the ESP and uses "efibootmgr" (on
 Linux) or "bless" (on OS X) to add rEFInd to the firmware's boot loader
 list. The docs/refind/installing.html file provides more details on this
 script and its use.
 

-If install.sh doesn't work for you or if you prefer to do the job manually,
-you may. On a UEFI-based system, you'll want to copy files on the ESP as
-follows:
+If refind-install doesn't work for you or if you prefer to do the job
+manually, you may. On a UEFI-based system, you'll want to copy files on the
+ESP as follows:

 
 * Create a directory for rEFInd, such as EFI/refind.
 * Copy refind/refind_ia32.efi or refind_x64.efi to the ESP's EFI/refind
 
 * Create a directory for rEFInd, such as EFI/refind.
 * Copy refind/refind_ia32.efi or refind_x64.efi to the ESP's EFI/refind


@@ -255,16 +255,16 @@ docs/refind/installing.html file for details.
 Note to Distribution Maintainers
 ================================
 
 Note to Distribution Maintainers
 ================================
 

-The install.sh script, and therefore the "install" target in the Makefile,
-installs the program directly to the ESP and it modifies the *CURRENT
-COMPUTER's* NVRAM. Thus, you should *NOT* use this target as part of the
-build process for your binary packages (RPMs, Debian packages, etc.).
-(Gentoo could use it in an ebuild, though....) You COULD, however, install
-the files to a directory somewhere (/usr/share/refind or whatever) and then
-call install.sh as part of the binary package installation process. Placing
-the files directly in /boot/efi/EFI/{distname}/refind and then having a
-post-install script call efibootmgr is probably the better way to go,
-but this assumes that the ESP is mounted at /boot/efi.
+The refind-install script, and therefore the "install" target in the
+Makefile, installs the program directly to the ESP and it modifies the
+*CURRENT COMPUTER's* NVRAM. Thus, you should *NOT* use this target as part
+of the build process for your binary packages (RPMs, Debian packages,
+etc.). (Gentoo could use it in an ebuild, though....) You COULD, however,
+install the files to a directory somewhere (/usr/share/refind or whatever)
+and then call refind-install as part of the binary package installation
+process. Placing the files directly in /boot/efi/EFI/{distname}/refind and
+then having a post-install script call efibootmgr is probably the better
+way to go, but this assumes that the ESP is mounted at /boot/efi.

 
 
 Compiling the EFI Filesystem Drivers
 
 
 Compiling the EFI Filesystem Drivers


@@ -282,10 +282,10 @@ builds with TianoCore.
 To install drivers, you can type "make install" in the "filesystems"
 directory. This copies all the drivers to the
 "/boot/efi/EFI/refind/drivers" directory. Alternatively, you can copy the
 To install drivers, you can type "make install" in the "filesystems"
 directory. This copies all the drivers to the
 "/boot/efi/EFI/refind/drivers" directory. Alternatively, you can copy the

-files you want manually. As of version 0.4.8, the install.sh script
-includes an optional "--drivers" option that will install the drivers along
-with the main rEFInd program, but to the drivers_{arch} subdirectory of the
-main rEFInd installation directory.
+files you want manually. The refind-install script includes an optional
+"--drivers" option that will install the drivers along with the main rEFInd
+program, but to the drivers_{arch} subdirectory of the main rEFInd
+installation directory.

 
 *CAUTION:* Install drivers for your system's architecture *ONLY*.
 Installing drivers for the wrong architecture causes some systems to hang
 
 *CAUTION:* Install drivers for your system's architecture *ONLY*.
 Installing drivers for the wrong architecture causes some systems to hang

diff --git a/Makefile b/Makefile
index c2616e8d2317749966710a7475f67d1bb3de7eb0..f611cb9e54cc3ca854840804b7b08a609eda0ec5 100644 (file)
--- a/Makefile
+++ b/Makefile
@@ -54,10 +54,10 @@ clean:
 # binary packages (RPMs, Debian packages, etc.). (Gentoo could
 # use it in an ebuild, though....) You COULD, however, copy the
 # files to a directory somewhere (/usr/share/refind or whatever)
 # binary packages (RPMs, Debian packages, etc.). (Gentoo could
 # use it in an ebuild, though....) You COULD, however, copy the
 # files to a directory somewhere (/usr/share/refind or whatever)

-# and then call install.sh as part of the binary package
+# and then call refind-install as part of the binary package

 # installation process.
 
 install:
 # installation process.
 
 install:

-       ./install.sh
+       ./refind-install

 
 # DO NOT DELETE
 
 # DO NOT DELETE

diff --git a/NEWS.txt b/NEWS.txt
index 9f30ead99e7e925a15286b8a0d68a203240ad823..f1222876c0859ef6c94f68af8909339578733126 100644 (file)
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -1,6 +1,9 @@
 0.9.3 (??/??/2015):
 -------------------
 
 0.9.3 (??/??/2015):
 -------------------
 

+- Renamed support scripts: install.sh to refind-install, mvrefind.sh to
+  mvrefind, and mkrlconf.sh to mkrlconf.
+

 - New icons! The old ones were getting to be a jumbled mess of styles,
   particularly for OS tags. I used the AwOken icon set
   (http://alecive.deviantart.com/art/AwOken-163570862) for the core icons,
 - New icons! The old ones were getting to be a jumbled mess of styles,
   particularly for OS tags. I used the AwOken icon set
   (http://alecive.deviantart.com/art/AwOken-163570862) for the core icons,

diff --git a/README.txt b/README.txt
index e79447c8139640e37fa4fdf9ab82f2d62393db80..4f86cb659615710828be8673a4d3deb9c2c2aa45 100644 (file)
--- a/README.txt
+++ b/README.txt
@@ -13,9 +13,9 @@ following files and subdirectories:
    refind/drivers_ia32/             Subdirectory containing IA32 drivers
    refind/drivers_x64/              Subdirectory containing x86-64 drivers
    keys/                            Subdirectory containing MOKs
    refind/drivers_ia32/             Subdirectory containing IA32 drivers
    refind/drivers_x64/              Subdirectory containing x86-64 drivers
    keys/                            Subdirectory containing MOKs

-   install.sh                       Linux/MacOS installation script
-   mkrlconf.sh                      A script to create refind_linux.conf
-   mvrefind.sh                      A script to move a rEFInd installation
+   refind-install                   Linux/MacOS installation script
+   mkrlconf                         A script to create refind_linux.conf
+   mvrefind                         A script to move a rEFInd installation

    README.txt                       This file
    NEWS.txt                         A summary of program changes
    LICENSE.txt                      The original rEFIt license
    README.txt                       This file
    NEWS.txt                         A summary of program changes
    LICENSE.txt                      The original rEFIt license


@@ -23,12 +23,12 @@ following files and subdirectories:
    CREDITS.txt                      Acknowledgments of code sources
    docs/                            Documentation in HTML format
 
    CREDITS.txt                      Acknowledgments of code sources
    docs/                            Documentation in HTML format
 

-The easiest way of installing rEFInd is generally to use the install.sh
+The easiest way of installing rEFInd is generally to use the refind-install

 script; however, you must be running under Linux or OS X to do this. If
 script; however, you must be running under Linux or OS X to do this. If

-you're using either of those OSes, simply typing "./install.sh" will
+you're using either of those OSes, simply typing "./refind-install" will

 generally install rEFInd. If you have problems with this method, though,
 generally install rEFInd. If you have problems with this method, though,

-you'll have to do a manual installation. The install.sh script supports a
-number of options that you might want to use; consult the
+you'll have to do a manual installation. The refind-install script supports
+a number of options that you might want to use; consult the

 docs/refind/installing.html file for details.
 
 To install the binary package manually, you must first access your EFI
 docs/refind/installing.html file for details.
 
 To install the binary package manually, you must first access your EFI


@@ -66,6 +66,6 @@ Brief Installation Instructions (Source Package)
 rEFInd source code can be obtained from
 https://sourceforge.net/projects/refind/. Consult the BUILDING.txt file in
 the source code package for build instructions. Once  you've built the
 rEFInd source code can be obtained from
 https://sourceforge.net/projects/refind/. Consult the BUILDING.txt file in
 the source code package for build instructions. Once  you've built the

-source code, you can use the install.sh script to install the binaries
+source code, you can use the refind-install script to install the binaries

 you've built. Alternatively, you can duplicate the directory tree described
 above by copying the individual files and the icons directory to the ESP.
 you've built. Alternatively, you can duplicate the directory tree described
 above by copying the individual files and the icons directory to the ESP.

diff --git a/debian/debinstall b/debian/debinstall
index 6140c4bfbe85eb20b9beb29405d8c94dc14db77f..6fc7d52296c111589215d3eb00115107acbc8b12 100755 (executable)
--- a/debian/debinstall
+++ b/debian/debinstall
@@ -39,7 +39,7 @@ fi
 install -Dp -m0644 refind.conf-sample $BUILD_ROOT/usr/share/refind/refind/
 cp -a icons $BUILD_ROOT/usr/share/refind/refind/
 rm -rf $BUILD_ROOT/usr/share/refind/refind/icons/svg
 install -Dp -m0644 refind.conf-sample $BUILD_ROOT/usr/share/refind/refind/
 cp -a icons $BUILD_ROOT/usr/share/refind/refind/
 rm -rf $BUILD_ROOT/usr/share/refind/refind/icons/svg

-install -Dp -m0755 install.sh $BUILD_ROOT/usr/share/refind/
+install -Dp -m0755 refind-install $BUILD_ROOT/usr/share/refind/

 
 # Copy documentation to /usr/share/doc/refind
 mkdir -p $BUILD_ROOT/usr/share/doc/refind
 
 # Copy documentation to /usr/share/doc/refind
 mkdir -p $BUILD_ROOT/usr/share/doc/refind


@@ -52,8 +52,8 @@ install -Dp -m0644 keys/* $BUILD_ROOT/etc/refind.d/keys
 
 # Copy scripts to /usr/sbin
 mkdir -p $BUILD_ROOT/usr/sbin
 
 # Copy scripts to /usr/sbin
 mkdir -p $BUILD_ROOT/usr/sbin

-install -Dp -m0755 mkrlconf.sh $BUILD_ROOT/usr/sbin/
-install -Dp -m0755 mvrefind.sh $BUILD_ROOT/usr/sbin/
+install -Dp -m0755 mkrlconf $BUILD_ROOT/usr/sbin/
+install -Dp -m0755 mvrefind $BUILD_ROOT/usr/sbin/

 
 # Copy banners and fonts to /usr/share/refind
 cp -a banners $BUILD_ROOT/usr/share/refind/
 
 # Copy banners and fonts to /usr/share/refind
 cp -a banners $BUILD_ROOT/usr/share/refind/

diff --git a/debian/postinst b/debian/postinst
index af54dbed586e8b86ed58b48c0795f5b257c5a08b..af7330876e687cd437255b4d86c55bf17ac55a2e 100755 (executable)
--- a/debian/postinst
+++ b/debian/postinst
@@ -37,14 +37,14 @@ declare OpenSSL=`which openssl 2> /dev/null`
 # their own local keys.
 if [[ $IsSecureBoot == "1" && -n $ShimFile ]] ; then
    if [[ -n $SBSign && -n $OpenSSL ]] ; then
 # their own local keys.
 if [[ $IsSecureBoot == "1" && -n $ShimFile ]] ; then
    if [[ -n $SBSign && -n $OpenSSL ]] ; then

-      ./install.sh --shim $ShimFile --localkeys --yes
+      ./refind-install --shim $ShimFile --localkeys --yes

    else
    else

-      ./install.sh --shim $ShimFile --yes
+      ./refind-install --shim $ShimFile --yes

    fi
 else
    if [[ -n $SBSign && -n $OpenSSL ]] ; then
    fi
 else
    if [[ -n $SBSign && -n $OpenSSL ]] ; then

-      ./install.sh --localkeys --yes
+      ./refind-install --localkeys --yes

    else
    else

-      ./install.sh --yes
+      ./refind-install --yes

    fi
 fi
    fi
 fi

diff --git a/docs/refind/drivers.html b/docs/refind/drivers.html
index 9b99a0005b17f6e5f31351fc44e5392da2d59eea..a497a71fe7103bc8d23333bbad8669c685fac87a 100644 (file)
--- a/docs/refind/drivers.html
+++ b/docs/refind/drivers.html
@@ -283,7 +283,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
 <p>All of these drivers rely on filesystem wrapper code written by rEFIt's author, Christoph Phisterer.</p>
 
 
 <p>All of these drivers rely on filesystem wrapper code written by rEFIt's author, Christoph Phisterer.</p>
 

-<p class="sidebar"><b>Note:</b> rEFInd's <tt>install.sh</tt> script, when run from Linux, installs the driver required to read the <tt>/boot</tt> directory. Under OS X, the <tt>install.sh</tt> script installs the ext4fs driver if the script detects a Linux partition&mdash;but you might need to change this driver if you use another filesystem. The script installs all the available drivers if you pass it the <tt>--alldrivers</tt> option. (I do <i>not</i> recommend using this feature except for creating general-purpose USB flash drives with rEFInd, since having too many drivers can cause various problems.) See the <a href="installing.html">Installing rEFInd</a> page for details.</p>
+<p class="sidebar"><b>Note:</b> rEFInd's <tt>refind-install</tt> script, when run from Linux, installs the driver required to read the <tt>/boot</tt> directory. Under OS X, the <tt>refind-install</tt> script installs the ext4fs driver if the script detects a Linux partition&mdash;but you might need to change this driver if you use another filesystem. The script installs all the available drivers if you pass it the <tt>--alldrivers</tt> option. (I do <i>not</i> recommend using this feature except for creating general-purpose USB flash drives with rEFInd, since having too many drivers can cause various problems.) See the <a href="installing.html">Installing rEFInd</a> page for details.</p>

 
 <p>If you want to use one or more of these drivers, you can install them from the rEFInd binary package from the <tt>refind/drivers_<tt class="variable">arch</tt></tt> directory, where <tt class="variable">arch</tt> is a CPU architecture code&mdash;<tt>x64</tt> or <tt>ia32</tt>. The files are named after the filesystems they handle, such as <tt>ext4_x64.efi</tt> for the 64-bit ext4fs driver. You should copy the files for the filesystems you want to use to the <tt>drivers</tt> or <tt>drivers_<tt class="variable">arch</tt></tt> subdirectory of the main rEFInd installation directory. (You may need to create this subdirectory.) Be careful to install drivers only for your own architecture. Attempting to load drivers for the wrong CPU type will cause a small delay at best, or may cause the computer to crash at worst. I've placed rEFInd's drivers in directories that are named to minimize this risk, but you should exercise care when copying driver files.</p>
 
 
 <p>If you want to use one or more of these drivers, you can install them from the rEFInd binary package from the <tt>refind/drivers_<tt class="variable">arch</tt></tt> directory, where <tt class="variable">arch</tt> is a CPU architecture code&mdash;<tt>x64</tt> or <tt>ia32</tt>. The files are named after the filesystems they handle, such as <tt>ext4_x64.efi</tt> for the 64-bit ext4fs driver. You should copy the files for the filesystems you want to use to the <tt>drivers</tt> or <tt>drivers_<tt class="variable">arch</tt></tt> subdirectory of the main rEFInd installation directory. (You may need to create this subdirectory.) Be careful to install drivers only for your own architecture. Attempting to load drivers for the wrong CPU type will cause a small delay at best, or may cause the computer to crash at worst. I've placed rEFInd's drivers in directories that are named to minimize this risk, but you should exercise care when copying driver files.</p>
 

diff --git a/docs/refind/getting.html b/docs/refind/getting.html
index f4720e9a08f4df6c2bb59d967a7cab8b60235d71..c3592229a9d8b65e04a0d269d0c92bc69aae2a12 100644 (file)
--- a/docs/refind/getting.html
+++ b/docs/refind/getting.html
@@ -158,11 +158,12 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
     binary RPM file</a></b>&mdash;If you use an RPM-based <i>x</i>86-64
     Linux system such as Fedora or openSUSE, you can install the binary RPM
     package rather than use the binary zip file. (I don't provide an
     binary RPM file</a></b>&mdash;If you use an RPM-based <i>x</i>86-64
     Linux system such as Fedora or openSUSE, you can install the binary RPM
     package rather than use the binary zip file. (I don't provide an

-    equivalent 32-bit package.) This package runs the <tt>install.sh</tt>
-    script (described on the <a href="installing.html">Installing
-    rEFInd</a> page) as part of the installation process. Distribution
-    maintainers can examine the <tt>refind.spec</tt> file in the source
-    package and tweak it to their needs. The <a
+    equivalent 32-bit package.) This package runs the
+    <tt>refind-install</tt> script (described on the <a
+    href="installing.html">Installing rEFInd</a> page) as part of the
+    installation process. Distribution maintainers can examine the
+    <tt>refind.spec</tt> file in the source package and tweak it to their
+    needs. The <a

     href="http://sourceforge.net/projects/refind/files/0.9.2/refind-0.9.2-1.src.rpm/download">source
     RPM file</a> might or might not build on your system as-is; it relies
     on assumptions about the locations of the GNU-EFI development
     href="http://sourceforge.net/projects/refind/files/0.9.2/refind-0.9.2-1.src.rpm/download">source
     RPM file</a> might or might not build on your system as-is; it relies
     on assumptions about the locations of the GNU-EFI development


@@ -196,12 +197,12 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
 <p class="sidebar"><b>Tip:</b> If you want to make your own bootable USB
 flash drive, download the binary zip file or CD-R image file, prepare a USB
 
 <p class="sidebar"><b>Tip:</b> If you want to make your own bootable USB
 flash drive, download the binary zip file or CD-R image file, prepare a USB

-flash drive with a FAT32 partition, and then use the <tt>install.sh</tt>
-program's <tt>--usedefault</tt> option, and perhaps the
-<tt>--alldrivers</tt> option, as in <tt class="userinput">bash install.sh
---usedefault /dev/sdd1 --alldrivers</tt> to install to the first partition
-on <tt>/dev/sdd</tt>. This procedure should work even on a BIOS-booted
-computer.</p>
+flash drive with a FAT32 partition, and then use the
+<tt>refind-install</tt> program's <tt>--usedefault</tt> option, and perhaps
+the <tt>--alldrivers</tt> option, as in <tt class="userinput">bash
+refind-install --usedefault /dev/sdd1 --alldrivers</tt> to install to the
+first partition on <tt>/dev/sdd</tt>. This procedure should work even on a
+BIOS-booted computer.</p>

 
 <li><b><a
     href="http://sourceforge.net/projects/refind/files/0.9.2/refind-flashdrive-0.9.2.zip/download">A
 
 <li><b><a
     href="http://sourceforge.net/projects/refind/files/0.9.2/refind-flashdrive-0.9.2.zip/download">A

diff --git a/docs/refind/installing.html b/docs/refind/installing.html
index 8497bf83e796215b797670549667403989c4f22e..64821acc38bc346c0b7d1336d05ce0b2f29d6b81 100644 (file)
--- a/docs/refind/installing.html
+++ b/docs/refind/installing.html
@@ -132,9 +132,9 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
 <div style="float:right; width:55%">
 
 
 <div style="float:right; width:55%">
 

-<p><b>Don't be scared by the length of this page!</b> Only portions of this page apply to any given user, and most people can install rEFInd from an RPM or Debian package in a matter of seconds or by using the <tt>install.sh</tt> script in minute or two.</p>
+<p><b>Don't be scared by the length of this page!</b> Only portions of this page apply to any given user, and most people can install rEFInd from an RPM or Debian package in a matter of seconds or by using the <tt>refind-install</tt> script in minute or two.</p>

 
 

-<p>Once you've obtained a rEFInd binary file, as described on <a href="getting.html">the preceding page,</a> you must install it to your computer's EFI System Partition (ESP) (or conceivably to some other location). The details of how you do this depend on your OS and your computer (UEFI-based PC vs. Macintosh). The upcoming sections provide details. See the Contents sidebar to the left for links to specific installation procedures. For most Linux users, an RPM or Debian package is the best way to go. If your Linux system doesn't support these formats, though, or if you're running OS X, using the <tt>install.sh</tt> script can be a good way to go. If you're using Windows, you'll have to install manually.</p>
+<p>Once you've obtained a rEFInd binary file, as described on <a href="getting.html">the preceding page,</a> you must install it to your computer's EFI System Partition (ESP) (or conceivably to some other location). The details of how you do this depend on your OS and your computer (UEFI-based PC vs. Macintosh). The upcoming sections provide details. See the Contents sidebar to the left for links to specific installation procedures. For most Linux users, an RPM or Debian package is the best way to go. If your Linux system doesn't support these formats, though, or if you're running OS X, using the <tt>refind-install</tt> script can be a good way to go. If you're using Windows, you'll have to install manually.</p>

 
 <p class="sidebar" style="width:95%"><b>Important:</b> A rEFInd zip file, when uncompressed, creates a directory called <tt>refind-<i>version</i></tt>, where <tt><i>version</i></tt> is the version number. This directory includes a subdirectory called <tt>refind</tt> that holds the rEFInd binary along with another that holds documentation, as well as miscellaneous files in <tt>refind-<i>version</i></tt> itself. When I refer to "the <tt>refind</tt> directory" on this page, I mean the directory with that precise name, not the <tt>refind-<i>version</i></tt> directory that is its parent.</p>
 
 
 <p class="sidebar" style="width:95%"><b>Important:</b> A rEFInd zip file, when uncompressed, creates a directory called <tt>refind-<i>version</i></tt>, where <tt><i>version</i></tt> is the version number. This directory includes a subdirectory called <tt>refind</tt> that holds the rEFInd binary along with another that holds documentation, as well as miscellaneous files in <tt>refind-<i>version</i></tt> itself. When I refer to "the <tt>refind</tt> directory" on this page, I mean the directory with that precise name, not the <tt>refind-<i>version</i></tt> directory that is its parent.</p>
 


@@ -148,13 +148,13 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
 <li class="tight"><a href="#packagefile">Installing rEFInd using an RPM or Debian package file</a></li>
 
 
 <li class="tight"><a href="#packagefile">Installing rEFInd using an RPM or Debian package file</a></li>
 

-<li class="tight"><a href="#installsh">Installing rEFInd Using <tt>install.sh</tt> under Linux or Mac OS X</a>
+<li class="tight"><a href="#installsh">Installing rEFInd Using <tt>refind-install</tt> under Linux or Mac OS X</a>

 
    <ul class="tight">
 
 
    <ul class="tight">
 

-   <li class="tight"><a href="#quickstart">Quick <tt>install.sh</tt> Instructions</a></li>
+   <li class="tight"><a href="#quickstart">Quick <tt>refind-install</tt> Instructions</a></li>

 
 

-   <li class="tight"><a href="#extra_installsh">Extra <tt>install.sh</tt> Instructions</a></li>
+   <li class="tight"><a href="#extra_installsh">Extra <tt>refind-install</tt> Instructions</a></li>

 
    </ul></li>
 
 
    </ul></li>
 


@@ -174,7 +174,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
    <ul>
 
 
    <ul>
 

-   <li class="tight"><a href="#mvrefind">Using <tt>mvrefind.sh</tt></li>
+   <li class="tight"><a href="#mvrefind">Using <tt>mvrefind</tt></li>

 
    <li class="tight"><a href="#manual_renaming">Renaming Files Manually</li>
 
 
    <li class="tight"><a href="#manual_renaming">Renaming Files Manually</li>
 


@@ -232,7 +232,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
 <pre class="listing"># <tt class="userinput">dpkg -i refind_0.9.2-1_amd64.deb</tt></pre>
 
 
 <pre class="listing"># <tt class="userinput">dpkg -i refind_0.9.2-1_amd64.deb</tt></pre>
 

-<p>Either command produces output similar to that described for <a href="#installsh">using the <tt>install.sh</tt> script,</a> so you can check it for error messages and other signs of trouble. The package file installs rEFInd and registers it with the EFI to be the default boot loader. The script that runs as part of the installation process tries to determine if you're using Secure Boot, and if so it will try to configure rEFInd to launch using shim; however, this won't work correctly on all systems. Ubuntu 12.10 users who are booting with Secure Boot active should be wary, since the resulting installation will probably try to use Ubuntu's version of shim, which won't work correctly with rEFInd. The shim program provided with more recent versions of Ubuntu should work correctly.</p>
+<p>Either command produces output similar to that described for <a href="#installsh">using the <tt>refind-install</tt> script,</a> so you can check it for error messages and other signs of trouble. The package file installs rEFInd and registers it with the EFI to be the default boot loader. The script that runs as part of the installation process tries to determine if you're using Secure Boot, and if so it will try to configure rEFInd to launch using shim; however, this won't work correctly on all systems. Ubuntu 12.10 users who are booting with Secure Boot active should be wary, since the resulting installation will probably try to use Ubuntu's version of shim, which won't work correctly with rEFInd. The shim program provided with more recent versions of Ubuntu should work correctly.</p>

 
 <a name="ppa">
 <p>If you're using Ubuntu, you should be able to install the PPA as follows:</p></a>
 
 <a name="ppa">
 <p>If you're using Ubuntu, you should be able to install the PPA as follows:</p></a>


@@ -243,33 +243,33 @@ $ <tt class="userinput">sudo apt-get install refind</tt></pre></pre>
 
 <p>The PPA version will update automatically with your other software, which you might or might not want to have happen. It's also built with GNU-EFI rather than with TianoCore. This last detail <i>should</i> have no practical effects, but it might be important if you've got a buggy EFI or if there's some undiscovered rEFInd bug that interacts with the build environment.</p>
 
 
 <p>The PPA version will update automatically with your other software, which you might or might not want to have happen. It's also built with GNU-EFI rather than with TianoCore. This last detail <i>should</i> have no practical effects, but it might be important if you've got a buggy EFI or if there's some undiscovered rEFInd bug that interacts with the build environment.</p>
 

-<p>Since version 0.6.3, the installation script makes an attempt to install rEFInd in a bootable way even if you run the script from a BIOS-mode boot, and therefore the RPM and Debian packages do the same. I cannot guarantee that this will work, though, and even if it does, some of the tricks that <tt>install.sh</tt> uses might not persist for long. You might therefore want to use <tt><a href="#mvrefind">mvrefind.sh</a></tt> to move your rEFInd installation to another name after you boot Linux for the first time from rEFInd.</p>
+<p>Since version 0.6.3, the installation script makes an attempt to install rEFInd in a bootable way even if you run the script from a BIOS-mode boot, and therefore the RPM and Debian packages do the same. I cannot guarantee that this will work, though, and even if it does, some of the tricks that <tt>refind-install</tt> uses might not persist for long. You might therefore want to use <tt><a href="#mvrefind">mvrefind</a></tt> to move your rEFInd installation to another name after you boot Linux for the first time from rEFInd.</p>

 
 

-<p>Since version 0.6.2-2, my package files have installed the rEFInd binaries to <tt>/usr/share/refind-<tt class="variable">version</tt></tt>, the documentation to <tt>/usr/share/doc/refind-<tt class="variable">version</tt></tt>, and a few miscellaneous files elsewhere. (The PPA package omits the version number from the file paths.) Upon installation, the package runs the <tt>install.sh</tt> script to copy the files to the ESP. This enables you to re-install rEFInd after the fact by running <tt>install.sh</tt>, should some other tool or OS wipe the ESP or should the installation go awry. In such cases you can <a href="#installsh">use <tt>install.sh</tt></a> or <a href="#manual">install manually.</a></p>
+<p>Since version 0.6.2-2, my package files have installed the rEFInd binaries to <tt>/usr/share/refind-<tt class="variable">version</tt></tt>, the documentation to <tt>/usr/share/doc/refind-<tt class="variable">version</tt></tt>, and a few miscellaneous files elsewhere. (The PPA package omits the version number from the file paths.) Upon installation, the package runs the <tt>refind-install</tt> script to copy the files to the ESP. This enables you to re-install rEFInd after the fact by running <tt>refind-install</tt>, should some other tool or OS wipe the ESP or should the installation go awry. In such cases you can <a href="#installsh">use <tt>refind-install</tt></a> or <a href="#manual">install manually.</a></p>

 
 <a name="installsh">
 
 <a name="installsh">

-<h2>Installing rEFInd Using <tt>install.sh</tt> under Linux or Mac OS X</h2>
+<h2>Installing rEFInd Using <tt>refind-install</tt> under Linux or Mac OS X</h2>

 
 

-<p class="sidebar"><b>Warning:</b> If you're using a Macintosh, you should run <tt>install.sh</tt> from Mac OS X rather than from Linux. If run from Linux, rEFInd is unlikely to be fully installed. The reason is that Apple uses non-standard methods to enable a boot loader, and the Linux functions in <tt>install.sh</tt> assume standard EFI installation methods.</p>
+<p class="sidebar"><b>Warning:</b> If you're using a Macintosh, you should run <tt>refind-install</tt> from Mac OS X rather than from Linux. If run from Linux, rEFInd is unlikely to be fully installed. The reason is that Apple uses non-standard methods to enable a boot loader, and the Linux functions in <tt>refind-install</tt> assume standard EFI installation methods.</p>

 
 

-<p>If you're using Linux or Mac OS X, the easiest way to install rEFInd is to use the <tt>install.sh</tt> script. This script automatically copies rEFInd's files to your ESP or other target location and makes changes to your firmware's NVRAM settings so that rEFInd will start the next time you boot. If you've booted to OS X or in non-Secure-Boot EFI mode to Linux on a UEFI-based PC, <tt>install.sh</tt> will probably do the right thing, so you can get by with the quick instructions. If your setup is unusual, if your computer uses Secure Boot, or if you want to create a USB flash drive with rEFInd on it, you should read the <a href="#extra_installsh">extra instructions</a> for this utility.</p>
+<p>If you're using Linux or Mac OS X, the easiest way to install rEFInd is to use the <tt>refind-install</tt> script. This script automatically copies rEFInd's files to your ESP or other target location and makes changes to your firmware's NVRAM settings so that rEFInd will start the next time you boot. If you've booted to OS X or in non-Secure-Boot EFI mode to Linux on a UEFI-based PC, <tt>refind-install</tt> will probably do the right thing, so you can get by with the quick instructions. If your setup is unusual, if your computer uses Secure Boot, or if you want to create a USB flash drive with rEFInd on it, you should read the <a href="#extra_installsh">extra instructions</a> for this utility.</p>

 
 <a name="quickstart">
 
 <a name="quickstart">

-<h3>Quick <tt>install.sh</tt> Instructions</h3>
+<h3>Quick <tt>refind-install</tt> Instructions</h3>

 </quickstart>
 
 <p class="sidebar"><b>Warning:</b> I've received reports that the OS X 10.11 ("El Capitan") beta has made changes to the OS that break the rEFInd installation procedure. This problem has been publicly reported as a bug in <tt>bless</tt>&mdash;see, for instance, <a href="http://www.openradar.me/22397509">here</a> and <a href="http://www.openradar.me/22170141">here.</a> It seems to be related to a new feature called System Integrity Protection. If possible, I recommend using OS X 10.10 ("Yosemite") or earlier to install rEFInd until this issue is resolved. It's reportedly possible to disable this feature by booting to recovery mode (by holding down Alt while booting) and typing <tt class="userinput">csrutil disable</tt> in a Terminal. After installing rEFInd, you can re-enable this feature by repeating the process, but typing <tt class="userinput">csrutil enable</tt>.</p>
 
 </quickstart>
 
 <p class="sidebar"><b>Warning:</b> I've received reports that the OS X 10.11 ("El Capitan") beta has made changes to the OS that break the rEFInd installation procedure. This problem has been publicly reported as a bug in <tt>bless</tt>&mdash;see, for instance, <a href="http://www.openradar.me/22397509">here</a> and <a href="http://www.openradar.me/22170141">here.</a> It seems to be related to a new feature called System Integrity Protection. If possible, I recommend using OS X 10.10 ("Yosemite") or earlier to install rEFInd until this issue is resolved. It's reportedly possible to disable this feature by booting to recovery mode (by holding down Alt while booting) and typing <tt class="userinput">csrutil disable</tt> in a Terminal. After installing rEFInd, you can re-enable this feature by repeating the process, but typing <tt class="userinput">csrutil enable</tt>.</p>
 

-<p>By default, the <tt>install.sh</tt> script installs rEFInd to your disk's ESP. Under Mac OS X, you can instead install rEFInd to your current OS X boot partition by passing the script the <tt>--notesp</tt> option, or to a non-boot HFS+ partition by using the <tt>--ownhfs <tt class="variable">devicefile</tt></tt> option. Under either OS, you can install to something other than the currently-running OS by using the <tt>--root <tt class="variable">/mountpoint</tt></tt> option. (See <a href="#table1">Table 1</a> for details.)</p>
+<p>By default, the <tt>refind-install</tt> script installs rEFInd to your disk's ESP. Under Mac OS X, you can instead install rEFInd to your current OS X boot partition by passing the script the <tt>--notesp</tt> option, or to a non-boot HFS+ partition by using the <tt>--ownhfs <tt class="variable">devicefile</tt></tt> option. Under either OS, you can install to something other than the currently-running OS by using the <tt>--root <tt class="variable">/mountpoint</tt></tt> option. (See <a href="#table1">Table 1</a> for details.)</p>

 
 

-<p>Under Linux, <tt>install.sh</tt> will be most reliable if your ESP is already mounted at <tt>/boot</tt> or <tt>/boot/efi</tt>, as described in more detail in the <a href="#linux">Installing rEFInd Manually Using Linux</a> section. (If you installed Linux in EFI mode, chances are your ESP is properly mounted.) If your ESP is not so mounted, <tt>install.sh</tt> will attempt to locate and mount an ESP, but this action is not guaranteed to work correctly. If you run <tt>install.sh</tt> from a BIOS/legacy-mode boot, particularly on a computer that also runs Windows, you should be aware that the tricks the script uses to install itself from BIOS mode are rather delicate. You can convert to a more conventional configuration using the <a href="#mvrefind"><tt>mvrefind.sh</tt> script</a> after you've booted in EFI mode.</p>
+<p>Under Linux, <tt>refind-install</tt> will be most reliable if your ESP is already mounted at <tt>/boot</tt> or <tt>/boot/efi</tt>, as described in more detail in the <a href="#linux">Installing rEFInd Manually Using Linux</a> section. (If you installed Linux in EFI mode, chances are your ESP is properly mounted.) If your ESP is not so mounted, <tt>refind-install</tt> will attempt to locate and mount an ESP, but this action is not guaranteed to work correctly. If you run <tt>refind-install</tt> from a BIOS/legacy-mode boot, particularly on a computer that also runs Windows, you should be aware that the tricks the script uses to install itself from BIOS mode are rather delicate. You can convert to a more conventional configuration using the <a href="#mvrefind"><tt>mvrefind</tt> script</a> after you've booted in EFI mode.</p>

 
 

-<p>Prior to version 0.8.4, <tt>install.sh</tt> installed rEFInd to the OS X root partition by default. I changed this because the default configuration for OS X 10.10 ("Yosemite") makes this placement unusable. Instead, <tt>install.sh</tt> now installs to the ESP under OS X, just as it does under Linux. <i>If you're upgrading a working install of rEFInd to the OS X root partition, it's best to pass the <tt>--notesp</tt> option to <tt>install.sh</tt>.</i> This option is described in more detail shortly.</p>
+<p>Prior to version 0.8.4, <tt>refind-install</tt> installed rEFInd to the OS X root partition by default. I changed this because the default configuration for OS X 10.10 ("Yosemite") makes this placement unusable. Instead, <tt>refind-install</tt> now installs to the ESP under OS X, just as it does under Linux. <i>If you're upgrading a working install of rEFInd to the OS X root partition, it's best to pass the <tt>--notesp</tt> option to <tt>refind-install</tt>.</i> This option is described in more detail shortly.</p>

 
 <p>A sample run under Linux looks something like this:</p>
 
 <pre class="listing">
 
 <p>A sample run under Linux looks something like this:</p>
 
 <pre class="listing">

-# <tt class="userinput">./install.sh</tt>
+# <tt class="userinput">./refind-install</tt>

 Installing rEFInd on Linux....
 ESP was found at /boot/efi using vfat
 Installing driver for ext4 (ext4_x64.efi)
 Installing rEFInd on Linux....
 ESP was found at /boot/efi using vfat
 Installing driver for ext4 (ext4_x64.efi)


@@ -284,7 +284,7 @@ Installation has completed successfully.</pre>
 <p>The output under OS X is a bit different:</p>
 
 <pre class="listing">
 <p>The output under OS X is a bit different:</p>
 
 <pre class="listing">

-$ <tt class="userinput">./install.sh</tt>
+$ <tt class="userinput">./refind-install</tt>

 Not running as root; attempting to elevate privileges via sudo....
 Password:
 Installing rEFInd on OS X....
 Not running as root; attempting to elevate privileges via sudo....
 Password:
 Installing rEFInd on OS X....


@@ -311,7 +311,7 @@ Unmounting install dir</pre>
 <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&mdash;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">
 <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&mdash;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>
+<h3>Extra <tt>refind-install</tt> Instructions</h3>

 </a>
 
 <p>Some details that can affect how the script runs include the following:</p>
 </a>
 
 <p>Some details that can affect how the script runs include the following:</p>


@@ -323,10 +323,10 @@ Unmounting install dir</pre>
     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
     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>
+    <tt>refind-install</tt> as <tt>root</tt>.</li>

 
 <li>Under OS X, you can run the script with a mouse by opening a Terminal
 
 <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
+    session and then dragging-and-dropping the <tt>refind-install</tt> file to

     the Terminal window. You'll need to press the Return or Enter key to
     run the script.</li>
 
     the Terminal window. You'll need to press the Return or Enter key to
     run the script.</li>
 


@@ -335,30 +335,30 @@ Unmounting install dir</pre>
     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
     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
+    class="variable">device-file</tt></tt> option to <tt>refind-install</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
     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
+    <tt>--notesp</tt> option to <tt>refind-install</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
     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
+    <tt>refind-install</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
     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
+    class="userinput">N</tt> when <tt>refind-install</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
     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
+    <tt>refind-install</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>
 
     --info</tt> to check your installation status; this combination has
     been reported to cause disk corruption on some Macs!</li>
 


@@ -368,7 +368,7 @@ Unmounting install dir</pre>
     though; because of the popularity of dual boots with Windows on Macs,
     the BIOS/legacy scans are enabled by default on Macs.</li>
 
     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
+<li>On Linux, <tt>refind-install</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>)
     <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>)


@@ -378,13 +378,13 @@ Unmounting install dir</pre>
     partition and if you mount that partition at <tt>/boot</tt> in your
     emergency system, and the ESP at <tt>/boot/efi</tt>.</li>
 
     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
+<li>On OS X, <tt>refind-install</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
     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
+    only under Linux. (The <tt>mkrlconf</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
     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


@@ -392,9 +392,9 @@ Unmounting install dir</pre>
     where <tt>/dev/<tt class="variable">whatever</tt></tt> is the device
     identifier of your Linux root (<tt>/</tt>) filesystem.
 
     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
+<li>If you run <tt>refind-install</tt> on Linux and if

     <tt>/boot/refind_linux.conf</tt> doesn't already exist,
     <tt>/boot/refind_linux.conf</tt> doesn't already exist,

-    <tt>install.sh</tt> creates this file and populates it with a few
+    <tt>refind-install</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
     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


@@ -409,28 +409,28 @@ Unmounting install dir</pre>
     renamed as <tt>grubx64.efi</tt>. Recent versions of shim support
     passing the name of the follow-on program to shim via a parameter,
     though. If you want to use this feature, you can pass the
     renamed as <tt>grubx64.efi</tt>. Recent versions of shim support
     passing the name of the follow-on program to shim via a parameter,
     though. If you want to use this feature, you can pass the

-    <tt>--keepname</tt> option to <tt>install.sh</tt>.</li>
+    <tt>--keepname</tt> option to <tt>refind-install</tt>.</li>

 
 </ul>
 
 
 </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>
+<p>In addition to these quirks, you should be aware of some options that <tt>refind-install</tt> supports to enable you to customize your installation in various ways. The syntax for <tt>refind-install</tt> is as follows:</p>

 
 <pre class="listing">
 
 <pre class="listing">

-install.sh [--notesp | --usedefault <tt class="variable">device-file</tt> | --root <tt class="variable">mount-point</tt> | \
+refind-install [--notesp | --usedefault <tt class="variable">device-file</tt> | --root <tt class="variable">mount-point</tt> | \

             --ownhfs <tt class="variable">device-file</tt> ] [--keepname ] \
            [--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>--notesp</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>
 
             --ownhfs <tt class="variable">device-file</tt> ] [--keepname ] \
            [--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>--notesp</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>
 

-<table border="1" cellpadding="1" cellspacing="2" summary="Table 1: Options to <tt>install.sh</tt>"><a name="table1"><caption><b>Table 1: Options to <tt>install.sh</tt></b></caption></a>
+<table border="1" cellpadding="1" cellspacing="2" summary="Table 1: Options to <tt>refind-install</tt>"><a name="table1"><caption><b>Table 1: Options to <tt>refind-install</tt></b></caption></a>

 <tr>
    <th>Option</th>
    <th>Explanation</th>
 </tr>
 <tr>
    <td><tt>--notesp</tt></td>
 <tr>
    <th>Option</th>
    <th>Explanation</th>
 </tr>
 <tr>
    <td><tt>--notesp</tt></td>

-   <td>This option, which is valid only under OS X, tells <tt>install.sh</tt> to install rEFInd to the OS X root partition rather than to the ESP. This behavior was the default in rEFInd 0.8.3 and earlier, so you may want to use it when upgrading installations of that version, unless you used <tt>--esp</tt> (which is now the default behavior, although the <tt>--esp</tt> option no longer exists) or <tt>--ownhfs</tt>. You may also want to use <tt>--notesp</tt> on new installations if you're sure you're <i>not</i> using whole-disk encryption or logical volumes.</td>
+   <td>This option, which is valid only under OS X, tells <tt>refind-install</tt> to install rEFInd to the OS X root partition rather than to the ESP. This behavior was the default in rEFInd 0.8.3 and earlier, so you may want to use it when upgrading installations of that version, unless you used <tt>--esp</tt> (which is now the default behavior, although the <tt>--esp</tt> option no longer exists) or <tt>--ownhfs</tt>. You may also want to use <tt>--notesp</tt> on new installations if you're sure you're <i>not</i> using whole-disk encryption or logical volumes.</td>

 </tr>
 <tr>
    <td><tt>--usedefault <tt class="variable">device-file</tt></tt></td>
 </tr>
 <tr>
    <td><tt>--usedefault <tt class="variable">device-file</tt></tt></td>


@@ -442,41 +442,41 @@ install.sh [--notesp | --usedefault <tt class="variable">device-file</tt> | --ro
 </tr>
 <tr>
    <td><tt>--root <tt class="variable">/mount-point</tt></tt></td>
 </tr>
 <tr>
    <td><tt>--root <tt class="variable">/mount-point</tt></tt></td>

-   <td>This option is intended to help install rEFInd from a "live CD" or other emergency system. To use it, you should mount your regular installation at <tt class="variable">/mount-point</tt>, including your <tt>/boot</tt> directory (if it's separate) at <tt class="variable">/mount-point</tt><tt>/boot</tt> and (on Linux) your ESP at that location or at <tt class="variable">/mount-point</tt><tt>/boot/efi</tt>. The <tt>install.sh</tt> script then installs rEFInd to the appropriate location&mdash;on Linux, <tt class="variable">/mount-point</tt><tt>/boot/EFI/refind</tt> or <tt class="variable">/mount-point</tt><tt>/boot/efi/EFI/refind</tt>, depending on where you've mounted your ESP. Under OS X, this option is only useful in conjunction with <tt>--notesp</tt>, in which case rEFInd will install to <tt class="variable">/mount-point</tt><tt>/EFI/refind</tt>. The script also adds an entry to your NVRAM for rEFInd at this location. You cannot use this option with <tt>--usedefault</tt>. Note that this option is <i>not</i> needed when doing a dual-boot Linux/OS X installation; just install normally in OS X.</td>
+   <td>This option is intended to help install rEFInd from a "live CD" or other emergency system. To use it, you should mount your regular installation at <tt class="variable">/mount-point</tt>, including your <tt>/boot</tt> directory (if it's separate) at <tt class="variable">/mount-point</tt><tt>/boot</tt> and (on Linux) your ESP at that location or at <tt class="variable">/mount-point</tt><tt>/boot/efi</tt>. The <tt>refind-install</tt> script then installs rEFInd to the appropriate location&mdash;on Linux, <tt class="variable">/mount-point</tt><tt>/boot/EFI/refind</tt> or <tt class="variable">/mount-point</tt><tt>/boot/efi/EFI/refind</tt>, depending on where you've mounted your ESP. Under OS X, this option is only useful in conjunction with <tt>--notesp</tt>, in which case rEFInd will install to <tt class="variable">/mount-point</tt><tt>/EFI/refind</tt>. The script also adds an entry to your NVRAM for rEFInd at this location. You cannot use this option with <tt>--usedefault</tt>. Note that this option is <i>not</i> needed when doing a dual-boot Linux/OS X installation; just install normally in OS X.</td>

 </tr>
 <tr>
    <td><tt>--nodrivers</tt></td>
 </tr>
 <tr>
    <td><tt>--nodrivers</tt></td>

-   <td>Ordinarily <tt>install.sh</tt> attempts to install the driver required to read <tt>/boot</tt> on Linux. This attempt works only if you're using ext2fs, ext3fs, ext4fs, or ReiserFS on the relevant partition. If you want to forego this driver installation, pass the <tt>--nodrivers</tt> option. This option is the implicit when you use <tt>--usedefault</tt>.</td>
+   <td>Ordinarily <tt>refind-install</tt> attempts to install the driver required to read <tt>/boot</tt> on Linux. This attempt works only if you're using ext2fs, ext3fs, ext4fs, or ReiserFS on the relevant partition. If you want to forego this driver installation, pass the <tt>--nodrivers</tt> option. This option is the implicit when you use <tt>--usedefault</tt>.</td>

 </tr>
 <tr>
    <td><tt>--alldrivers</tt></td>
 </tr>
 <tr>
    <td><tt>--alldrivers</tt></td>

-   <td>When you specify this option, <tt>install.sh</tt> copies <i>all</i> the driver files for your architecture. You may want to remove unused driver files after you use this option, especially if your computer uses Secure Boot. Note that some computers hang or fail to work with any drivers if you use this option, so use it with caution.</td>
+   <td>When you specify this option, <tt>refind-install</tt> copies <i>all</i> the driver files for your architecture. You may want to remove unused driver files after you use this option, especially if your computer uses Secure Boot. Note that some computers hang or fail to work with any drivers if you use this option, so use it with caution.</td>

 </tr>
 <tr>
    <td><tt>--shim <tt class="variable">shim-filename</tt></tt> or <tt>--preloader <tt class="variable">preloader-filename</tt></tt></td>
 </tr>
 <tr>
    <td><tt>--shim <tt class="variable">shim-filename</tt></tt> or <tt>--preloader <tt class="variable">preloader-filename</tt></tt></td>

-   <td>If you pass this option to <tt>install.sh</tt>, the script will copy the specified shim program file to the target directory, copy the <tt>MokManager.efi</tt> file from the shim program file's directory to the target directory, copy the 64-bit version of rEFInd as <tt>grubx64.efi</tt>, and register shim with the firmware. (If you also specify <tt>--usedefault</tt>, the NVRAM registration is skipped. If you also use <tt>--keepname</tt>, the renaming to <tt>grubx64.efi</tt> is skipped.) When the target file is identified as PreLoader, much the same thing happens, but <tt>install.sh</tt> copies <tt>HashTool.efi</tt> instead of <tt>MokManager.efi</tt> and copies rEFInd as <tt>loader.efi</tt> rather than as <tt>grubx64.efi</tt>. The intent is to simplify rEFInd installation on a computer that uses Secure Boot; when so set up, rEFInd will boot in Secure Boot mode, with one caveat: The first time you boot, MokManager/HashTool will launch, and you must use it to locate and install a public key or register rEFInd as a trusted application. The rEFInd public key file will be located in the rEFInd directory's <tt>keys</tt> subdirectory under the name <tt>refind.cer</tt>. Note that I'm not providing a shim binary myself, but you can download one from <a href="http://www.codon.org.uk/~mjg59/shim-signed/">here.</a> Some distributions also provide their own shim programs, so can point to them&mdash;for instance, in <tt>/boot/efi/EFI/fedora/shim.efi</tt>.</td>
+   <td>If you pass this option to <tt>refind-install</tt>, the script will copy the specified shim program file to the target directory, copy the <tt>MokManager.efi</tt> file from the shim program file's directory to the target directory, copy the 64-bit version of rEFInd as <tt>grubx64.efi</tt>, and register shim with the firmware. (If you also specify <tt>--usedefault</tt>, the NVRAM registration is skipped. If you also use <tt>--keepname</tt>, the renaming to <tt>grubx64.efi</tt> is skipped.) When the target file is identified as PreLoader, much the same thing happens, but <tt>refind-install</tt> copies <tt>HashTool.efi</tt> instead of <tt>MokManager.efi</tt> and copies rEFInd as <tt>loader.efi</tt> rather than as <tt>grubx64.efi</tt>. The intent is to simplify rEFInd installation on a computer that uses Secure Boot; when so set up, rEFInd will boot in Secure Boot mode, with one caveat: The first time you boot, MokManager/HashTool will launch, and you must use it to locate and install a public key or register rEFInd as a trusted application. The rEFInd public key file will be located in the rEFInd directory's <tt>keys</tt> subdirectory under the name <tt>refind.cer</tt>. Note that I'm not providing a shim binary myself, but you can download one from <a href="http://www.codon.org.uk/~mjg59/shim-signed/">here.</a> Some distributions also provide their own shim programs, so can point to them&mdash;for instance, in <tt>/boot/efi/EFI/fedora/shim.efi</tt>.</td>

 </tr>
 <tr>
    <td><tt>--localkeys</tt></td>
 </tr>
 <tr>
    <td><tt>--localkeys</tt></td>

-   <td>This option tells <tt>install.sh</tt> to generate a new Machine Owner Key (MOK), store it in <tt>/etc/refind.d/keys</tt> as <tt>refind_local.*</tt>, and re-sign all the 64-bit rEFInd binaries with this key before installing them. This is the preferable way to install rEFInd in Secure Boot mode, since it means your binaries will be signed locally rather than with my own key, which is used to sign many other users' binaries; however, this method requires that both the <tt>openssl</tt> and <tt>sbsign</tt> binaries be installed. The former is readily available in most distributions' repositories, but the latter is not, so this option is not the default.</td>
+   <td>This option tells <tt>refind-install</tt> to generate a new Machine Owner Key (MOK), store it in <tt>/etc/refind.d/keys</tt> as <tt>refind_local.*</tt>, and re-sign all the 64-bit rEFInd binaries with this key before installing them. This is the preferable way to install rEFInd in Secure Boot mode, since it means your binaries will be signed locally rather than with my own key, which is used to sign many other users' binaries; however, this method requires that both the <tt>openssl</tt> and <tt>sbsign</tt> binaries be installed. The former is readily available in most distributions' repositories, but the latter is not, so this option is not the default.</td>

 </tr>
 <tr>
    <td><tt>--keepname</tt></td>
 </tr>
 <tr>
    <td><tt>--keepname</tt></td>

-   <td>This option is useful only in conjunction with <tt>--shim</tt>. It tells <tt>install.sh</tt> to keep rEFInd's regular filename (typically <tt>refind_x64.efi</tt>) when used with shim, rather than rename the binary to <tt>grubx64.efi</tt>. This change cuts down on the chance of confusion because of filename issues; however, this feature requires that shim be launched with a command-line parameter that points to the rEFInd binary under its real name. versions of shim prior to 0.7 do not properly support this feature. (Version 0.4 supports it but with a buggy interpretation of the follow-on loader specification.) If your NVRAM variables become corrupted or are forgotten, this feature may make rEFInd harder to launch. This option is incompatible with <tt>--usedefault</tt> and is unavailable when run under OS X or without the <tt>--shim</tt> option. If the script discovers an existing rEFInd installation under <tt>EFI/BOOT</tt> or <tt>EFI/Microsoft/Boot</tt> and no other rEFInd installation when this option is used, it will abort.</td>
+   <td>This option is useful only in conjunction with <tt>--shim</tt>. It tells <tt>refind-install</tt> to keep rEFInd's regular filename (typically <tt>refind_x64.efi</tt>) when used with shim, rather than rename the binary to <tt>grubx64.efi</tt>. This change cuts down on the chance of confusion because of filename issues; however, this feature requires that shim be launched with a command-line parameter that points to the rEFInd binary under its real name. versions of shim prior to 0.7 do not properly support this feature. (Version 0.4 supports it but with a buggy interpretation of the follow-on loader specification.) If your NVRAM variables become corrupted or are forgotten, this feature may make rEFInd harder to launch. This option is incompatible with <tt>--usedefault</tt> and is unavailable when run under OS X or without the <tt>--shim</tt> option. If the script discovers an existing rEFInd installation under <tt>EFI/BOOT</tt> or <tt>EFI/Microsoft/Boot</tt> and no other rEFInd installation when this option is used, it will abort.</td>

 </tr>
 <tr>
    <td><tt>--yes</tt></td>
 </tr>
 <tr>
    <td><tt>--yes</tt></td>

-   <td>This option causes the script to assume a <tt>Y</tt> input to every yes/no prompt that can be generated under certain conditions, such as if you specify <tt>--shim</tt> but <tt>install.sh</tt> detects no evidence of a Secure Boot installation. This option is intended mainly for use by scripts such as those that might be used as part of an installation via an RPM or Debian package.</td>
+   <td>This option causes the script to assume a <tt>Y</tt> input to every yes/no prompt that can be generated under certain conditions, such as if you specify <tt>--shim</tt> but <tt>refind-install</tt> detects no evidence of a Secure Boot installation. This option is intended mainly for use by scripts such as those that might be used as part of an installation via an RPM or Debian package.</td>

 </tr>
 </table>
 
 </tr>
 </table>
 

-<p>After you run <tt>install.sh</tt>, 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>
+<p>After you run <tt>refind-install</tt>, you should peruse the script's output to ensure that everything looks OK. <tt>refind-install</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>

 
 <a name="manual">
 <h2>Installing rEFInd Manually</h2>
 </a>
 
 
 <a name="manual">
 <h2>Installing rEFInd Manually</h2>
 </a>
 

-<p>Sometimes the <tt>install.sh</tt> script just won't do the job, or you may need to install using an OS that it doesn't support, such as Windows. In these cases, you'll have to install rEFInd the old-fashioned way, using file-copying commands and utilities to add the program to your EFI's boot loader list. I describe how to do this with <a href="#linux">Linux</a>, <a href="#osx">OS X</a>, <a href="#windows">Windows</a>, and <a href="#efishell">the EFI shell.</a></p>
+<p>Sometimes the <tt>refind-install</tt> script just won't do the job, or you may need to install using an OS that it doesn't support, such as Windows. In these cases, you'll have to install rEFInd the old-fashioned way, using file-copying commands and utilities to add the program to your EFI's boot loader list. I describe how to do this with <a href="#linux">Linux</a>, <a href="#osx">OS X</a>, <a href="#windows">Windows</a>, and <a href="#efishell">the EFI shell.</a></p>

 
 <a name="linux">
 <h3>Installing rEFInd Manually Using Linux</h3>
 
 <a name="linux">
 <h3>Installing rEFInd Manually Using Linux</h3>


@@ -803,16 +803,16 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
 
 </ul>
 
 
 </ul>
 

-<p>If you need to use one of these names, or something more exotic, you can do so in either of two ways: You can <a href="#mvrefind">use the <tt>mvrefind.sh</tt> script</a> to move your installation in one step, or you can <a href="#manual_renaming">move and rename your files manually.</a></p>
+<p>If you need to use one of these names, or something more exotic, you can do so in either of two ways: You can <a href="#mvrefind">use the <tt>mvrefind</tt> script</a> to move your installation in one step, or you can <a href="#manual_renaming">move and rename your files manually.</a></p>

 
 <a name="mvrefind">
 
 <a name="mvrefind">

-<h3>Using <tt>mvrefind.sh</tt></h3>
+<h3>Using <tt>mvrefind</tt></h3>

 </a>
 
 </a>
 

-<p>The easiest way to move a rEFInd installation, at least in Linux, is to use the <tt>mvrefind.sh</tt> script. If you installed from one of my RPM or Debian packages, this script should be installed in <tt>/usr/sbin</tt>, so you can use it like a regular Linux command; otherwise you'll need to install it to your path yourself or type its complete path. Either way, it works much like the Linux <tt>mv</tt> command, but you pass it the directory in which a rEFInd installation appears and a target location:</p>
+<p>The easiest way to move a rEFInd installation, at least in Linux, is to use the <tt>mvrefind</tt> script. If you installed from one of my RPM or Debian packages, this script should be installed in <tt>/usr/sbin</tt>, so you can use it like a regular Linux command; otherwise you'll need to install it to your path yourself or type its complete path. Either way, it works much like the Linux <tt>mv</tt> command, but you pass it the directory in which a rEFInd installation appears and a target location:</p>

 
 <pre class="listing">
 
 <pre class="listing">

-# <tt class="userinput">mvrefind.sh /boot/efi/EFI/BOOT /boot/efi/EFI/refind</tt>
+# <tt class="userinput">mvrefind /boot/efi/EFI/BOOT /boot/efi/EFI/refind</tt>

 </pre>
 
 <p>This example moves rEFInd from <tt>/boot/efi/EFI/BOOT</tt> to <tt>/boot/efi/EFI/refind</tt>. It differs from <tt>mv</tt> in several ways:
 </pre>
 
 <p>This example moves rEFInd from <tt>/boot/efi/EFI/BOOT</tt> to <tt>/boot/efi/EFI/refind</tt>. It differs from <tt>mv</tt> in several ways:


@@ -820,7 +820,7 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
 <ul>
 
 <li>The script renames rEFInd in a way that's sensitive to its source and
 <ul>
 
 <li>The script renames rEFInd in a way that's sensitive to its source and

-    destination directories&mdash;for instance, <tt>mvrefind.sh</tt> knows
+    destination directories&mdash;for instance, <tt>mvrefind</tt> knows

     that rEFInd (or shim, for Secure Boot installations) must be called
     <tt>bootx64.efi</tt> on a 64-bit installation in
     <tt>/boot/efi/EFI/BOOT</tt>, so it looks for rEFInd under that name
     that rEFInd (or shim, for Secure Boot installations) must be called
     <tt>bootx64.efi</tt> on a 64-bit installation in
     <tt>/boot/efi/EFI/BOOT</tt>, so it looks for rEFInd under that name


@@ -841,7 +841,7 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
 
 </ul>
 
 
 </ul>
 

-<p>The <tt>mvrefind.sh</tt> script is likely to be useful in resolving boot problems&mdash;if your system won't boot, you can try copying the installation to <tt>/boot/efi/EFI/BOOT</tt>, <tt>/boot/efi/EFI/Microsoft/Boot</tt>, and <tt>/boot/efi/EFI/refind</tt> in turn, testing the boot process after each attempt. (These filenames all assume your ESP is mounted at <tt>/boot/efi</tt>.) You could also copy a BIOS-mode install from <tt>/boot/efi/EFI/BOOT</tt> or <tt>/boot/efi/EFI/Microsoft/Boot</tt> to <tt>/boot/efi/EFI/refind</tt> to make it more robust against Windows repairs (assuming your firmware isn't broken).</p>
+<p>The <tt>mvrefind</tt> script is likely to be useful in resolving boot problems&mdash;if your system won't boot, you can try copying the installation to <tt>/boot/efi/EFI/BOOT</tt>, <tt>/boot/efi/EFI/Microsoft/Boot</tt>, and <tt>/boot/efi/EFI/refind</tt> in turn, testing the boot process after each attempt. (These filenames all assume your ESP is mounted at <tt>/boot/efi</tt>.) You could also copy a BIOS-mode install from <tt>/boot/efi/EFI/BOOT</tt> or <tt>/boot/efi/EFI/Microsoft/Boot</tt> to <tt>/boot/efi/EFI/refind</tt> to make it more robust against Windows repairs (assuming your firmware isn't broken).</p>

 
 <a name="manual_renaming">
 <h3>Renaming Files Manually</h3>
 
 <a name="manual_renaming">
 <h3>Renaming Files Manually</h3>


@@ -890,24 +890,24 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
 <li>In OS X, if you copy over the original file with the new one, you'll
     probably have to re-bless it to make it work.</li>
 
 <li>In OS X, if you copy over the original file with the new one, you'll
     probably have to re-bless it to make it work.</li>
 

-<li>Under Linux or OS X, you can re-run the <tt>install.sh</tt> script. In
+<li>Under Linux or OS X, you can re-run the <tt>refind-install</tt> script. In

     most cases this works fine, but you'll end up with a duplicate of the
     icons directory (<tt>icons-backup</tt>, which holds the original icons,
     whereas <tt>icons</tt> holds the icons from the new package). Normally
     this just wastes some disk space; but if you've customized your icons,
     you'll need to copy your altered icons back. Under Linux, versions
     most cases this works fine, but you'll end up with a duplicate of the
     icons directory (<tt>icons-backup</tt>, which holds the original icons,
     whereas <tt>icons</tt> holds the icons from the new package). Normally
     this just wastes some disk space; but if you've customized your icons,
     you'll need to copy your altered icons back. Under Linux, versions

-    0.6.2 and later of <tt>install.sh</tt> search for rEFInd in several
+    0.6.2 and later of <tt>refind-install</tt> search for rEFInd in several

     locations on the ESP, and will upgrade whatever is found. The same is
     true with versions 0.8.5 and later under OS X when installing to the
     ESP. If you install to a location other than the ESP under OS X, be
     locations on the ESP, and will upgrade whatever is found. The same is
     true with versions 0.8.5 and later under OS X when installing to the
     ESP. If you install to a location other than the ESP under OS X, be

-    sure to include the same option to <tt>install.sh</tt>
+    sure to include the same option to <tt>refind-install</tt>

     (<tt>--notesp</tt> or <tt>--ownhfs</tt>) to replace the original rather
     than create a new installation to the ESP.</li>
 
 <li>Under an RPM- or Debian-based Linux distribution, you can use your
     package system to install a newer version of the RPM or Debian package
     that I provide. This will upgrade the files in your Linux filesystem
     (<tt>--notesp</tt> or <tt>--ownhfs</tt>) to replace the original rather
     than create a new installation to the ESP.</li>
 
 <li>Under an RPM- or Debian-based Linux distribution, you can use your
     package system to install a newer version of the RPM or Debian package
     that I provide. This will upgrade the files in your Linux filesystem

-    and re-run the <tt>install.sh</tt> script, so as with the previous
+    and re-run the <tt>refind-install</tt> script, so as with the previous

     options, you'll waste a little disk space on duplicated icons, but the
     process should otherwise work quite well.</li>
 
     options, you'll waste a little disk space on duplicated icons, but the
     process should otherwise work quite well.</li>
 


@@ -917,14 +917,14 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
     on how the package was created, though, this update might or might not
     install the update to the ESP; you might need to manually re-run the
     installation script. Consult your distribution's documentation for
     on how the package was created, though, this update might or might not
     install the update to the ESP; you might need to manually re-run the
     installation script. Consult your distribution's documentation for

-    details. My Ubuntu PPA will automatically run <tt>install.sh</tt> after
+    details. My Ubuntu PPA will automatically run <tt>refind-install</tt> after

     the package is installed.</li>
 
 </ul>
 
     the package is installed.</li>
 
 </ul>
 

-<p>In all cases, if the new version includes new or altered configuration file options, you may need to manually update your configuration file. Alternatively, if you've used the default configuration file, you can replace your working <tt>refind.conf</tt> with <tt>refind.conf-sample</tt> from the rEFInd zip file. (When using <tt>install.sh</tt>, this file will be copied to rEFInd's installation directory under its original name, so you can rename it within that directory to replace the old file.)</p>
+<p>In all cases, if the new version includes new or altered configuration file options, you may need to manually update your configuration file. Alternatively, if you've used the default configuration file, you can replace your working <tt>refind.conf</tt> with <tt>refind.conf-sample</tt> from the rEFInd zip file. (When using <tt>refind-install</tt>, this file will be copied to rEFInd's installation directory under its original name, so you can rename it within that directory to replace the old file.)</p>

 
 

-<p>If you're upgrading to rEFInd from rEFIt, you can simply run the <tt>install.sh</tt> script as described earlier or perform a manual installation. Once installed, rEFInd will take over boot manager duties. You'll still be able to launch rEFIt from rEFInd; a rEFIt icon will appear in rEFInd's menu. You can eliminate this option by removing the rEFIt files, which normally reside in <tt>/EFI/refit</tt>.</p>
+<p>If you're upgrading to rEFInd from rEFIt, you can simply run the <tt>refind-install</tt> script as described earlier or perform a manual installation. Once installed, rEFInd will take over boot manager duties. You'll still be able to launch rEFIt from rEFInd; a rEFIt icon will appear in rEFInd's menu. You can eliminate this option by removing the rEFIt files, which normally reside in <tt>/EFI/refit</tt>.</p>

 
 <a name="addons">
 <h2>Installing Additional Components</h2>
 
 <a name="addons">
 <h2>Installing Additional Components</h2>


@@ -984,7 +984,7 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
     original rEFIt version of the program usually goes by the filename
     <tt>gptsync.efi</tt>, whereas the updated rEFInd version ships with an
     architecture code, as in <tt>gptsync_x64.efi</tt> or
     original rEFIt version of the program usually goes by the filename
     <tt>gptsync.efi</tt>, whereas the updated rEFInd version ships with an
     architecture code, as in <tt>gptsync_x64.efi</tt> or

-    <tt>gptsync_ia32.efi</tt>. The rEFInd <tt>install.sh</tt> script
+    <tt>gptsync_ia32.efi</tt>. The rEFInd <tt>refind-install</tt> script

     installs <tt>gptsync_<tt class="variable">arch</tt>.efi</tt> when run
     under OS X, but not when run on Linux. In addition to installing the
     program, you must edit <tt>refind.conf</tt>, uncomment the
     installs <tt>gptsync_<tt class="variable">arch</tt>.efi</tt> when run
     under OS X, but not when run on Linux. In addition to installing the
     program, you must edit <tt>refind.conf</tt>, uncomment the


@@ -1034,7 +1034,7 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
 <h3>Using the <tt>--shortform</tt> Option</h3>
 </a>
 
 <h3>Using the <tt>--shortform</tt> Option</h3>
 </a>
 

-<p>Prior to version 0.8.5, these instructions and the <tt>install.sh</tt> script omitted the <tt>--shortform</tt> option from the <tt>bless</tt> command when installing rEFInd to the ESP. An rEFInd user, however, discovered that using the option eliminated the 30-second delay, so it is now the default with 0.8.5's <tt>install.sh</tt>, and is specified in the instructions. If you installed rEFInd 0.8.4 or earlier, you may want to re-install or re-<tt>bless</tt> rEFInd using this option.</p>
+<p>Prior to version 0.8.5, these instructions and the <tt>refind-install</tt> script omitted the <tt>--shortform</tt> option from the <tt>bless</tt> command when installing rEFInd to the ESP. An rEFInd user, however, discovered that using the option eliminated the 30-second delay, so it is now the default with 0.8.5's <tt>refind-install</tt>, and is specified in the instructions. If you installed rEFInd 0.8.4 or earlier, you may want to re-install or re-<tt>bless</tt> rEFInd using this option.</p>

 
 <p>There is one caveat, though: The <tt>man</tt> page for <tt>bless</tt> notes that <tt>--shortform</tt> notes that its use can come "at the expense of boot time performance." Thus, it's not clear to me that this option might not actually <i>create</i> problems on some computers. (It's eliminated the boot delay on my 2014 MacBook Air and has no detrimental effect on an old 32-bit Mac Mini that's never had a boot delay problem, though.) Thus, if you have problems with rEFInd 0.8.5 or later, you might try running <tt>bless</tt>, as described in <a href="#osx">Installing rEFInd Manually Using OS X's</a> step 8, but <i>omit</i> the <tt>--shortform</tt> option.</p>
 
 
 <p>There is one caveat, though: The <tt>man</tt> page for <tt>bless</tt> notes that <tt>--shortform</tt> notes that its use can come "at the expense of boot time performance." Thus, it's not clear to me that this option might not actually <i>create</i> problems on some computers. (It's eliminated the boot delay on my 2014 MacBook Air and has no detrimental effect on an old 32-bit Mac Mini that's never had a boot delay problem, though.) Thus, if you have problems with rEFInd 0.8.5 or later, you might try running <tt>bless</tt>, as described in <a href="#osx">Installing rEFInd Manually Using OS X's</a> step 8, but <i>omit</i> the <tt>--shortform</tt> option.</p>
 


@@ -1042,7 +1042,7 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
 <h3>Using the Fallback Filename</h3>
 </a>
 
 <h3>Using the Fallback Filename</h3>
 </a>
 

-<p>I've received a few reports that installing rEFInd to the ESP using the fallback filename (<tt>EFI/BOOT/bootx64.efi</tt> on most systems, or <tt>EFI/BOOT/bootia32.efi</tt> on very old Macs) can work around a sluggish boot problem. In fact, version 0.8.4's <tt>install.sh</tt> script copied the rEFInd binary to this name when run under OS X. (Version 0.8.5 switches to using <tt>--shortform</tt> with the more conventional <tt>EFI/refind/refind_x64.efi</tt> or <tt>EFI/refind/refind_ia32.efi</tt> name, as just noted.) If you installed to a name other than <tt>EFI/BOOT/BOOT<tt class="variable">{ARCH}</tt></tt>, either manually or by using the 0.8.5 or later <tt>install.sh</tt>, renaming (and re-<tt>bless</tt>ing) the installation is worth trying.</p>
+<p>I've received a few reports that installing rEFInd to the ESP using the fallback filename (<tt>EFI/BOOT/bootx64.efi</tt> on most systems, or <tt>EFI/BOOT/bootia32.efi</tt> on very old Macs) can work around a sluggish boot problem. In fact, version 0.8.4's <tt>refind-install</tt> script copied the rEFInd binary to this name when run under OS X. (Version 0.8.5 switches to using <tt>--shortform</tt> with the more conventional <tt>EFI/refind/refind_x64.efi</tt> or <tt>EFI/refind/refind_ia32.efi</tt> name, as just noted.) If you installed to a name other than <tt>EFI/BOOT/BOOT<tt class="variable">{ARCH}</tt></tt>, either manually or by using the 0.8.5 or later <tt>refind-install</tt>, renaming (and re-<tt>bless</tt>ing) the installation is worth trying.</p>

 
 <a name="moving">
 <h3>Moving rEFInd to an HFS+ Volume</h3>
 
 <a name="moving">
 <h3>Moving rEFInd to an HFS+ Volume</h3>


@@ -1050,7 +1050,7 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
 
 <p>Most of the reports of sluggish Macintosh boots I've seen note that the user installed rEFInd to the ESP rather than to the OS X root partition. Some users have reported that re-installing rEFInd to the OS X root partition clears up the problem. This is obviously a straightforward solution to the problem, if it works. (This location is not an option when using WDE or OS X logical volumes.) Note that rEFInd can launch boot loaders that are stored on any partition that the EFI can read no matter where it's installed; therefore, you'll still be able to launch boot loaders stored on the ESP (or elsewhere) if you install it in this way.</p>
 
 
 <p>Most of the reports of sluggish Macintosh boots I've seen note that the user installed rEFInd to the ESP rather than to the OS X root partition. Some users have reported that re-installing rEFInd to the OS X root partition clears up the problem. This is obviously a straightforward solution to the problem, if it works. (This location is not an option when using WDE or OS X logical volumes.) Note that rEFInd can launch boot loaders that are stored on any partition that the EFI can read no matter where it's installed; therefore, you'll still be able to launch boot loaders stored on the ESP (or elsewhere) if you install it in this way.</p>
 

-<p>A variant of this solution is to create a small (~100MiB) HFS+ volume to be used exclusively by rEFInd. You can then install rEFInd to that volume with the <tt>--ownhfs</tt> option to <tt>install.sh</tt>, as in <tt class="userinput">./install.sh --ownhfs /dev/disk0s6</tt> if the volume is <tt>/dev/disk0s6</tt>. This approach has the advantage that it can be managed via OS X's own Startup Disk tool in System Preferences.</p>
+<p>A variant of this solution is to create a small (~100MiB) HFS+ volume to be used exclusively by rEFInd. You can then install rEFInd to that volume with the <tt>--ownhfs</tt> option to <tt>refind-install</tt>, as in <tt class="userinput">./refind-install --ownhfs /dev/disk0s6</tt> if the volume is <tt>/dev/disk0s6</tt>. This approach has the advantage that it can be managed via OS X's own Startup Disk tool in System Preferences.</p>

 
 <p>The biggest drawback to storing rEFInd on an HFS+ volume is that you won't be able to edit the rEFInd configuration file or move rEFInd-related binaries from an EFI shell if you install it in this way, since Apple's HFS+ driver for EFI is read-only. (The same is true of rEFInd's HFS+ driver, so it won't help you overcome this limitation.) You may also be limited in making changes to your rEFInd configuration from Linux or other OSes, too, since Linux's HFS+ drivers disable write support by default on volumes with an active journal. You can force write access by using the <tt>force</tt> option to <tt>mount</tt>; however, this procedure is noted as being risky in the Linux HFS+ documentation, so I don't recommend doing this on a regular basis on the OS X boot volume. This isn't as risky if you use a dedicated HFS+ rEFInd partition, though. You could even mount it as the Linux <tt>/boot</tt> partition, in which case it would also hold the Linux kernel and related files.</p>
 
 
 <p>The biggest drawback to storing rEFInd on an HFS+ volume is that you won't be able to edit the rEFInd configuration file or move rEFInd-related binaries from an EFI shell if you install it in this way, since Apple's HFS+ driver for EFI is read-only. (The same is true of rEFInd's HFS+ driver, so it won't help you overcome this limitation.) You may also be limited in making changes to your rEFInd configuration from Linux or other OSes, too, since Linux's HFS+ drivers disable write support by default on volumes with an active journal. You can force write access by using the <tt>force</tt> option to <tt>mount</tt>; however, this procedure is noted as being risky in the Linux HFS+ documentation, so I don't recommend doing this on a regular basis on the OS X boot volume. This isn't as risky if you use a dedicated HFS+ rEFInd partition, though. You could even mount it as the Linux <tt>/boot</tt> partition, in which case it would also hold the Linux kernel and related files.</p>
 


@@ -1082,7 +1082,7 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
 
 <ul>
 
 
 <ul>
 

-<li>Install rEFInd to an HFS+ volume using the <tt>--ownhfs</tt> option to <tt>install.sh</tt>. Unfortunately, this solution requires either creating a small HFS+ volume for rEFInd or using an already-existing non-bootable HFS+ volume (if you've got one for data storage, for example).</li>
+<li>Install rEFInd to an HFS+ volume using the <tt>--ownhfs</tt> option to <tt>refind-install</tt>. Unfortunately, this solution requires either creating a small HFS+ volume for rEFInd or using an already-existing non-bootable HFS+ volume (if you've got one for data storage, for example).</li>

 
 <li>Type <tt class="userinput">sudo pmset -a autopoweroff 0</tt> in a Terminal window. This solution is likely to work if sleep operations work normally up to a point, but fail after about three hours.</li>
 
 
 <li>Type <tt class="userinput">sudo pmset -a autopoweroff 0</tt> in a Terminal window. This solution is likely to work if sleep operations work normally up to a point, but fail after about three hours.</li>
 


@@ -1192,7 +1192,7 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
        it will be in <tt>EFI/refind</tt> or <tt>EFI/BOOT</tt> on the
        ESP.</li>
 
        it will be in <tt>EFI/refind</tt> or <tt>EFI/BOOT</tt> on the
        ESP.</li>
 

-    <li>If you used the <tt>--ownhfs</tt> option to <tt>install.sh</tt>,
+    <li>If you used the <tt>--ownhfs</tt> option to <tt>refind-install</tt>,

        rEFInd will be in the <tt>System/Library/CoreServices</tt>
        directory on the volume you specified.</li>
 
        rEFInd will be in the <tt>System/Library/CoreServices</tt>
        directory on the volume you specified.</li>
 


@@ -1202,7 +1202,7 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
     <li>In all cases, there could be duplicate (inactive) rEFInd files in
        unexpected places. This is particularly true if you tried
        installing rEFInd multiple times, each with different options to
     <li>In all cases, there could be duplicate (inactive) rEFInd files in
        unexpected places. This is particularly true if you tried
        installing rEFInd multiple times, each with different options to

-       <tt>install.sh</tt>. Thus, if you delete rEFInd and it still comes
+       <tt>refind-install</tt>. Thus, if you delete rEFInd and it still comes

        up, you may have deleted the wrong files. (Note that dragging files
        to the Trash may have no effect, though&mdash;at least, not until
        you empty the Trash.)</li>
        up, you may have deleted the wrong files. (Note that dragging files
        to the Trash may have no effect, though&mdash;at least, not until
        you empty the Trash.)</li>


@@ -1220,7 +1220,7 @@ $ <b>ioreg -l -p IODeviceTree | grep firmware-abi</b>
     <tt>System/Library/CoreServices</tt> directory,</i></b> since that's
     the default location of the OS X boot loader! <i>Never</i> delete this
     directory from your OS X root (<tt>/</tt>) partition, only from the
     <tt>System/Library/CoreServices</tt> directory,</i></b> since that's
     the default location of the OS X boot loader! <i>Never</i> delete this
     directory from your OS X root (<tt>/</tt>) partition, only from the

-    partition you specified to <tt>install.sh</tt> using the
+    partition you specified to <tt>refind-install</tt> using the

     <tt>--ownhfs</tt> option.</li>
 
 <li>Once you've identified the rEFInd directory, delete it, or at least the
     <tt>--ownhfs</tt> option.</li>
 
 <li>Once you've identified the rEFInd directory, delete it, or at least the

diff --git a/docs/refind/linux.html b/docs/refind/linux.html
index 274f234046ed39c8468c039dc0bdda065daae69b..559874801904b9895ef28347891eff30171d641e 100644 (file)
--- a/docs/refind/linux.html
+++ b/docs/refind/linux.html
@@ -186,7 +186,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
 <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>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>
 
 
 <ul>
 


@@ -196,7 +196,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
     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>
     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>
     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>


@@ -234,7 +234,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
 <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
 
 <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>
 
     with rEFInd. This step may not be strictly necessary if <tt>/boot</tt>
     is an ordinary directory on your root (<tt>/</tt>) partition.</li>
 


@@ -298,7 +298,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
     <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>/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
     later.</li>
 
 <li>Check your <tt>refind.conf</tt> file (presumably in


@@ -391,7 +391,7 @@ extends it as follows:</p>
     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
     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
     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


@@ -457,7 +457,7 @@ total 17943
 
 <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>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>
 
 
 <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>
 

diff --git a/docs/refind/refind-background-snowy.png b/docs/refind/refind-background-snowy.png
index bd15c59da53f0253603a43de832bce0758dd124e..b8c7815acf60ac979f7e8edec08b08c936d21bf3 100644 (file)
Binary files a/docs/refind/refind-background-snowy.png and b/docs/refind/refind-background-snowy.png differ

diff --git a/docs/refind/secureboot.html b/docs/refind/secureboot.html
index fc3f321763ad4ea40a2fa535f15f5f1247c7d182..09d382a110a1a7eda0273785f26c88eab769e1d9 100644 (file)
--- a/docs/refind/secureboot.html
+++ b/docs/refind/secureboot.html
@@ -228,7 +228,7 @@ Windows 8, this isn't an option for it. Unfortunately, the Shim and PreLoader pr
 <h3>Installing Shim and rEFInd</h3>
 </a>
 
 <h3>Installing Shim and rEFInd</h3>
 </a>
 

-<p class="sidebar"><b>Note:</b> rEFInd's <tt>install.sh</tt> script attempts to identify whether your computer was booted with Secure Boot active and, if it was, to locate existing Shim binaries and make use of whatever it finds. Thus, you may not need to explicitly set up Shim after you install rEFInd, although you will probably have to enroll rEFInd's key in your MOK list, as described shortly.</p>
+<p class="sidebar"><b>Note:</b> rEFInd's <tt>refind-install</tt> script attempts to identify whether your computer was booted with Secure Boot active and, if it was, to locate existing Shim binaries and make use of whatever it finds. Thus, you may not need to explicitly set up Shim after you install rEFInd, although you will probably have to enroll rEFInd's key in your MOK list, as described shortly.</p>

 
 <p>A working Secure Boot installation of rEFInd involves at least three programs, and probably four or more, each of which must be installed in a specific way:</p>
 
 
 <p>A working Secure Boot installation of rEFInd involves at least three programs, and probably four or more, each of which must be installed in a specific way:</p>
 


@@ -244,7 +244,7 @@ Windows 8, this isn't an option for it. Unfortunately, the Shim and PreLoader pr
 
 </ul>
 
 
 </ul>
 

-<p>If you've installed a distribution that provides Shim and can boot it with Secure Boot active, and if you then install rEFInd using the RPM file that I provide or by running <tt>install.sh</tt>, chances are you'll end up with a working rEFInd that will start up the first time, with one caveat: You'll have to use MokManager to add rEFInd's MOK to your MOK list, as described shortly. If you don't already have a working copy of Shim on your ESP, your task is more complex. Broadly speaking, the procedure should be something like this:</p>
+<p>If you've installed a distribution that provides Shim and can boot it with Secure Boot active, and if you then install rEFInd using the RPM file that I provide or by running <tt>refind-install</tt>, chances are you'll end up with a working rEFInd that will start up the first time, with one caveat: You'll have to use MokManager to add rEFInd's MOK to your MOK list, as described shortly. If you don't already have a working copy of Shim on your ESP, your task is more complex. Broadly speaking, the procedure should be something like this:</p>

 
 <ol>
 
 
 <ol>
 


@@ -262,7 +262,7 @@ Windows 8, this isn't an option for it. Unfortunately, the Shim and PreLoader pr
     version, though; as noted earlier, it's inadequate for use with
     rEFInd.)</li>
 
     version, though; as noted earlier, it's inadequate for use with
     rEFInd.)</li>
 

-<p class="sidebar"><b>Tip:</b> If you're running Linux, you can save some effort by using the <tt>install.sh</tt> script with its <tt>--shim <tt class="variable">/path/to/shim.efi</tt></tt> option rather than installing manually, as in steps 4&ndash;6 of this procedure. If you've installed <tt>openssl</tt> and <tt>sbsign</tt>, using <tt>--localkeys</tt> will generate local signing keys and re-sign the rEFInd binaries with your own key, too. You can then use <tt>sbsign</tt> and the keys in <tt>/etc/refind.d/keys</tt> to sign your kernels or boot loaders.</p>
+<p class="sidebar"><b>Tip:</b> If you're running Linux, you can save some effort by using the <tt>refind-install</tt> script with its <tt>--shim <tt class="variable">/path/to/shim.efi</tt></tt> option rather than installing manually, as in steps 4&ndash;6 of this procedure. If you've installed <tt>openssl</tt> and <tt>sbsign</tt>, using <tt>--localkeys</tt> will generate local signing keys and re-sign the rEFInd binaries with your own key, too. You can then use <tt>sbsign</tt> and the keys in <tt>/etc/refind.d/keys</tt> to sign your kernels or boot loaders.</p>

 
 <li>Copy the <tt>shim.efi</tt> and <tt>MokManager.efi</tt> binaries to the
     directory you intend to use for rEFInd&mdash;for instance,
 
 <li>Copy the <tt>shim.efi</tt> and <tt>MokManager.efi</tt> binaries to the
     directory you intend to use for rEFInd&mdash;for instance,


@@ -333,7 +333,7 @@ Windows 8, this isn't an option for it. Unfortunately, the Shim and PreLoader pr
 <h3>Managing Your MOKs</h3>
 </a>
 
 <h3>Managing Your MOKs</h3>
 </a>
 

-<p>The preceding instructions provided the basics of getting rEFInd up and running, including using MokManager to enroll a MOK on your computer. If you need to sign binaries, though, you'll have to use additional tools. The OpenSSL package provides the cryptographic tools necessary, but actually signing EFI binaries requires additional software. Two packages for this are available: <tt>sbsigntool</tt> and <tt>pesign</tt>. Both are available in binary form from <a href="https://build.opensuse.org/project/show?project=home%3Ajejb1%3AUEFI">this OpenSUSE Build Service (OBS)</a> repository, and many distributions ship with at least one of them. The following procedure uses <tt>sbsigntool</tt>. To sign your own binaries, follow these steps (you can skip the first five steps if you've successfully used <tt>install.sh</tt>'s <tt>--localkeys</tt> option):</p>
+<p>The preceding instructions provided the basics of getting rEFInd up and running, including using MokManager to enroll a MOK on your computer. If you need to sign binaries, though, you'll have to use additional tools. The OpenSSL package provides the cryptographic tools necessary, but actually signing EFI binaries requires additional software. Two packages for this are available: <tt>sbsigntool</tt> and <tt>pesign</tt>. Both are available in binary form from <a href="https://build.opensuse.org/project/show?project=home%3Ajejb1%3AUEFI">this OpenSUSE Build Service (OBS)</a> repository, and many distributions ship with at least one of them. The following procedure uses <tt>sbsigntool</tt>. To sign your own binaries, follow these steps (you can skip the first five steps if you've successfully used <tt>refind-install</tt>'s <tt>--localkeys</tt> option):</p>

 
 <ol>
 
 
 <ol>
 


@@ -341,8 +341,8 @@ Windows 8, this isn't an option for it. Unfortunately, the Shim and PreLoader pr
     normally comes in a package called <tt>openssl</tt>.)</li>
 
 <li>If you did <i>not</i> re-sign your rEFInd binaries with
     normally comes in a package called <tt>openssl</tt>.)</li>
 
 <li>If you did <i>not</i> re-sign your rEFInd binaries with

-    <tt>install.sh</tt>'s <tt>--localkeys</tt> option, type the following
-    two commands to generate your public and private keys:
+    <tt>refind-install</tt>'s <tt>--localkeys</tt> option, type the
+    following two commands to generate your public and private keys:

 
 <pre class="listing">
 $ <tt class="userinput">openssl req -new -x509 -newkey rsa:2048 -keyout refind_local.key \
 
 <pre class="listing">
 $ <tt class="userinput">openssl req -new -x509 -newkey rsa:2048 -keyout refind_local.key \


@@ -362,7 +362,7 @@ $ <tt class="userinput">openssl x509 -in refind_local.crt -out refind_local.cer
     are equivalent, but are used by different
     tools&mdash;<tt>sbsigntool</tt> uses <tt>refind_local.crt</tt> to sign
     binaries, but MokManager uses <tt>refind_local.cer</tt> to enroll the
     are equivalent, but are used by different
     tools&mdash;<tt>sbsigntool</tt> uses <tt>refind_local.crt</tt> to sign
     binaries, but MokManager uses <tt>refind_local.cer</tt> to enroll the

-    key. If you used <tt>install.sh</tt>'s <tt>--localkeys</tt> option,
+    key. If you used <tt>refind-install</tt>'s <tt>--localkeys</tt> option,

     this step is unnecessary, since these keys have already been created
     and are stored in <tt>/etc/refind.d/keys/</tt>.</li>
 
     this step is unnecessary, since these keys have already been created
     and are stored in <tt>/etc/refind.d/keys/</tt>.</li>
 

diff --git a/docs/refind/themes.html b/docs/refind/themes.html
index 3cfb5b7c935cbd46eea80d6349667ccd7c08ac1a..0092e1ce82d52aeb04b001215e6087d67a551d34 100644 (file)
--- a/docs/refind/themes.html
+++ b/docs/refind/themes.html
@@ -218,7 +218,7 @@ graphics, so you can change them.</p>
 
 <li>You can create new icons, place them in a subdirectory of rEFInd's main directory, and tell the program to use the new icons by setting the <tt>icons_dir</tt> token in <tt>refind.conf</tt>. This will affect the appearance of the OS tags, the utility tags, and so on. The names of these icons should match those in the <tt>icons</tt> subdirectory (although you can substitute ICNS for PNG files, with a suitable filename change), and are fairly self-explanatory. The default size for OS tags is 128x128 pixels, tags for 2nd-row utilities are ordinarily 48x48 pixels, and drive-type badges are 32x32 pixels by default. If an icon is missing from the directory specified by <tt>icons_dir</tt>, rEFInd falls back to the icon from the standard <tt>icons</tt> subdirectory; thus, you can replace just a subset of the standard icons. rEFInd can use icons in either Apple's <a href="http://en.wikipedia.org/wiki/Apple_Icon_Image">icon image (ICNS)</a> or <a href="http://en.wikipedia.org/wiki/Portable_Network_Graphics">Portable Network Graphics (PNG)</a> format. PNG files are easier to generate on most platforms. You can generate ICNS files in various Apple programs or by using the <a href="http://icns.sourceforge.net/">libicns</a> library (and in particular its <tt>png2icns</tt> program) in Linux.</li>
 
 
 <li>You can create new icons, place them in a subdirectory of rEFInd's main directory, and tell the program to use the new icons by setting the <tt>icons_dir</tt> token in <tt>refind.conf</tt>. This will affect the appearance of the OS tags, the utility tags, and so on. The names of these icons should match those in the <tt>icons</tt> subdirectory (although you can substitute ICNS for PNG files, with a suitable filename change), and are fairly self-explanatory. The default size for OS tags is 128x128 pixels, tags for 2nd-row utilities are ordinarily 48x48 pixels, and drive-type badges are 32x32 pixels by default. If an icon is missing from the directory specified by <tt>icons_dir</tt>, rEFInd falls back to the icon from the standard <tt>icons</tt> subdirectory; thus, you can replace just a subset of the standard icons. rEFInd can use icons in either Apple's <a href="http://en.wikipedia.org/wiki/Apple_Icon_Image">icon image (ICNS)</a> or <a href="http://en.wikipedia.org/wiki/Portable_Network_Graphics">Portable Network Graphics (PNG)</a> format. PNG files are easier to generate on most platforms. You can generate ICNS files in various Apple programs or by using the <a href="http://icns.sourceforge.net/">libicns</a> library (and in particular its <tt>png2icns</tt> program) in Linux.</li>
 

-<li>You can do as above, but place your new icons in the default <tt>icons</tt> subdirectory. This method is discouraged because using the <tt>install.sh</tt> script to upgrade rEFInd will replace your customized icons.</li>
+<li>You can do as above, but place your new icons in the default <tt>icons</tt> subdirectory. This method is discouraged because using the <tt>refind-install</tt> script to upgrade rEFInd will replace your customized icons.</li>

 
 <li>You can customize the appearance of an individual boot loader by placing an ICNS or PNG file in its directory with the same name as the boot loader but with a <tt>.icns</tt> or <tt>.png</tt> extension. For instance, if your boot loader program is <tt>elilo.efi</tt>, you can create a custom icon by naming it <tt>elilo.png</tt>.</li>
 
 
 <li>You can customize the appearance of an individual boot loader by placing an ICNS or PNG file in its directory with the same name as the boot loader but with a <tt>.icns</tt> or <tt>.png</tt> extension. For instance, if your boot loader program is <tt>elilo.efi</tt>, you can create a custom icon by naming it <tt>elilo.png</tt>.</li>
 

diff --git a/docs/refind/todo.html b/docs/refind/todo.html
index 6f28a860ca5fd6aa014e5fa8709286fc33f39068..bc63fc42ded32668848ddf843449f505c7b59f97 100644 (file)
--- a/docs/refind/todo.html
+++ b/docs/refind/todo.html
@@ -409,7 +409,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
     </ul></li> <!-- Drivers -->
 
 
     </ul></li> <!-- Drivers -->
 

-<li><b>Improvements to <tt>gptsync</tt>, <tt>install.sh</tt>, or other
+<li><b>Improvements to <tt>gptsync</tt>, <tt>refind-install</tt>, or other

     support tools:</b>
 
     <ul>
     support tools:</b>
 
     <ul>

diff --git a/mkdistrib b/mkdistrib
index c2f785f251859d11b4c22f75ce02119226e94016..9be32c971bd883532eb797d0d23e7356e3cc9f47 100755 (executable)
--- a/mkdistrib
+++ b/mkdistrib
@@ -52,7 +52,7 @@ mkdir -p ../snapshots/$1/refind-$1/icons/licenses ../snapshots/$1/refind-$1/icon
 cp --preserve=timestamps icons/*png icons/README ../snapshots/$1/refind-$1/icons/
 cp --preserve=timestamps -r icons/licenses/* ../snapshots/$1/refind-$1/icons/licenses/
 cp --preserve=timestamps -r icons/svg/* ../snapshots/$1/refind-$1/icons/svg/
 cp --preserve=timestamps icons/*png icons/README ../snapshots/$1/refind-$1/icons/
 cp --preserve=timestamps -r icons/licenses/* ../snapshots/$1/refind-$1/icons/licenses/
 cp --preserve=timestamps -r icons/svg/* ../snapshots/$1/refind-$1/icons/svg/

-cp -a debian docs images keys fonts banners include EfiLib libeg mok net refind filesystems gptsync refind.spec install.sh mkrlconf.sh mvrefind.sh CREDITS.txt NEWS.txt BUILDING.txt COPYING.txt LICENSE.txt README.txt refind.inf Make.tiano Make.common Makefile refind.conf-sample ../snapshots/$1/refind-$1
+cp -a debian docs images keys fonts banners include EfiLib libeg mok net refind filesystems gptsync refind.spec refind-install mkrlconf mvrefind CREDITS.txt NEWS.txt BUILDING.txt COPYING.txt LICENSE.txt README.txt refind.inf Make.tiano Make.common Makefile refind.conf-sample ../snapshots/$1/refind-$1

 
 # Go there and prepare a souce code tarball....
 cd ../snapshots/$1/
 
 # Go there and prepare a souce code tarball....
 cd ../snapshots/$1/


@@ -102,7 +102,7 @@ else
    cp --preserve=timestamps gptsync/gptsync_x64.efi refind-bin-$1/refind/tools_x64/
 fi
 cp refind-bin-$1/refind/refind_x64.efi $StartDir
    cp --preserve=timestamps gptsync/gptsync_x64.efi refind-bin-$1/refind/tools_x64/
 fi
 cp refind-bin-$1/refind/refind_x64.efi $StartDir

-cp -a docs keys banners fonts COPYING.txt LICENSE.txt README.txt CREDITS.txt NEWS.txt install.sh mkrlconf.sh mvrefind.sh refind-bin-$1
+cp -a docs keys banners fonts COPYING.txt LICENSE.txt README.txt CREDITS.txt NEWS.txt refind-install mkrlconf mvrefind refind-bin-$1

 
 # Prepare the final .zip file
 zip -9r ../refind-bin-$1.zip refind-bin-$1
 
 # Prepare the final .zip file
 zip -9r ../refind-bin-$1.zip refind-bin-$1

diff --git a/mkrlconf.sh b/mkrlconf
similarity index 93%
rename from mkrlconf.sh
rename to mkrlconf
index 478cd4487a67d732be3a95b349f7397b8727db5e..f6369c7a70bdf71dcfbe221aed471668b45b7cd2 100755 (executable)
--- a/mkrlconf.sh
+++ b/mkrlconf
@@ -10,7 +10,7 @@
 
 # Usage:
 #
 
 # Usage:
 #

-# ./mkrlconf.sh [--force]
+# ./mkrlconf [--force]

 #
 # Options:
 #
 #
 # Options:
 #


@@ -18,11 +18,12 @@
 
 # Revision history:
 #
 
 # Revision history:
 #

+#  0.9.3 -- Renamed from mkrlconf.sh to mkrlconf

 #  0.9.0 -- Added check for OS type, to keep from running pointlessly on OS X
 #  0.7.7 -- Fixed bug that caused stray PARTUUID= and line breaks in generated file
 #  0.5.1 -- Initial release
 #
 #  0.9.0 -- Added check for OS type, to keep from running pointlessly on OS X
 #  0.7.7 -- Fixed bug that caused stray PARTUUID= and line breaks in generated file
 #  0.5.1 -- Initial release
 #

-# Note: mkrlconf.sh version numbers match those of the rEFInd package
+# Note: mkrlconf version numbers match those of the rEFInd package

 # with which they first appeared.
 
 RLConfFile="/boot/refind_linux.conf"
 # with which they first appeared.
 
 RLConfFile="/boot/refind_linux.conf"

diff --git a/mvrefind.sh b/mvrefind
similarity index 98%
rename from mvrefind.sh
rename to mvrefind
index b1e14ec840a641464f99c10b71e2e639a7662fa2..6b16a1a0eaf9ba8db570e903416e3396dff16878 100755 (executable)
--- a/mvrefind.sh
+++ b/mvrefind
@@ -4,7 +4,7 @@
 #
 # Usage:
 #
 #
 # Usage:
 #

-# ./mvrefind.sh /path/to/source /path/to/destination
+# ./mvrefind /path/to/source /path/to/destination

 #
 # Typically used to "hijack" or "unhijack" a Windows boot loader location or
 # to help convert a rEFInd installation made in BIOS mode to one that works
 #
 # Typically used to "hijack" or "unhijack" a Windows boot loader location or
 # to help convert a rEFInd installation made in BIOS mode to one that works


@@ -12,9 +12,10 @@
 #
 # Revision history:
 #
 #
 # Revision history:
 #

+# 0.9.3   -- Renamed from mvrefind.sh to mvrefind

 # 0.6.3   -- Initial release
 #
 # 0.6.3   -- Initial release
 #

-# Note: mvrefind.sh version numbers match those of the rEFInd package
+# Note: mvrefind version numbers match those of the rEFInd package

 # with which they first appeared.
 
 RootDir="/"
 # with which they first appeared.
 
 RootDir="/"

diff --git a/install.sh b/refind-install
similarity index 99%
rename from install.sh
rename to refind-install
index a503820647542a748abf745547e9c7c18c2f5545..cd9b07b1dfe7e0f5575f5dae468e676ff8e19ae9 100755 (executable)
--- a/install.sh
+++ b/refind-install
@@ -4,7 +4,7 @@
 #
 # Usage:
 #
 #
 # Usage:
 #

-# ./install.sh [options]
+# ./refind-install [options]

 #
 # options include:
 #    "--notesp" to install to the OS X root filesystem rather than to the ESP.
 #
 # options include:
 #    "--notesp" to install to the OS X root filesystem rather than to the ESP.

diff --git a/refind.spec b/refind.spec
index fb63d6c9c7ce567c4703c2f4bf676dc1d7cbab25..267e2be495e8c6c2f9790f412b335e60cd718ae2 100644 (file)
--- a/refind.spec
+++ b/refind.spec
@@ -86,7 +86,7 @@ fi
 install -Dp -m0644 refind.conf-sample $RPM_BUILD_ROOT/usr/share/refind-%{version}/refind/
 cp -a icons $RPM_BUILD_ROOT/usr/share/refind-%{version}/refind/
 rm -rf $RPM_BUILD_ROOT/usr/share/refind-%{version}/refind/icons/svg
 install -Dp -m0644 refind.conf-sample $RPM_BUILD_ROOT/usr/share/refind-%{version}/refind/
 cp -a icons $RPM_BUILD_ROOT/usr/share/refind-%{version}/refind/
 rm -rf $RPM_BUILD_ROOT/usr/share/refind-%{version}/refind/icons/svg

-install -Dp -m0755 install.sh $RPM_BUILD_ROOT/usr/share/refind-%{version}/
+install -Dp -m0755 refind-install $RPM_BUILD_ROOT/usr/share/refind-%{version}/

 
 # Copy documentation to /usr/share/doc/refind-%{version}
 mkdir -p $RPM_BUILD_ROOT/usr/share/doc/refind-%{version}
 
 # Copy documentation to /usr/share/doc/refind-%{version}
 mkdir -p $RPM_BUILD_ROOT/usr/share/doc/refind-%{version}


@@ -99,8 +99,8 @@ install -Dp -m0644 keys/* $RPM_BUILD_ROOT/etc/refind.d/keys
 
 # Copy scripts to /usr/sbin
 mkdir -p $RPM_BUILD_ROOT/usr/sbin
 
 # Copy scripts to /usr/sbin
 mkdir -p $RPM_BUILD_ROOT/usr/sbin

-install -Dp -m0755 mkrlconf.sh $RPM_BUILD_ROOT/usr/sbin/
-install -Dp -m0755 mvrefind.sh $RPM_BUILD_ROOT/usr/sbin/
+install -Dp -m0755 mkrlconf $RPM_BUILD_ROOT/usr/sbin/
+install -Dp -m0755 mvrefind $RPM_BUILD_ROOT/usr/sbin/

 
 # Copy banners and fonts to /usr/share/refind-%{version}
 cp -a banners $RPM_BUILD_ROOT/usr/share/refind-%{version}/
 
 # Copy banners and fonts to /usr/share/refind-%{version}
 cp -a banners $RPM_BUILD_ROOT/usr/share/refind-%{version}/


@@ -112,8 +112,8 @@ cp -a fonts $RPM_BUILD_ROOT/usr/share/refind-%{version}/
 %files
 %defattr(-,root,root -)
 %doc /usr/share/doc/refind-%{version}
 %files
 %defattr(-,root,root -)
 %doc /usr/share/doc/refind-%{version}

-/usr/sbin/mkrlconf.sh
-/usr/sbin/mvrefind.sh
+/usr/sbin/mkrlconf
+/usr/sbin/mvrefind

 /usr/share/refind-%{version}
 /etc/refind.d/
 
 /usr/share/refind-%{version}
 /etc/refind.d/
 


@@ -151,21 +151,21 @@ declare OpenSSL=`which openssl 2> /dev/null`
 # encourage users to use their own local keys.
 if [[ $IsSecureBoot == "1" && -n $ShimFile ]] ; then
    if [[ -n $SBSign && -n $OpenSSL ]] ; then
 # encourage users to use their own local keys.
 if [[ $IsSecureBoot == "1" && -n $ShimFile ]] ; then
    if [[ -n $SBSign && -n $OpenSSL ]] ; then

-      ./install.sh --shim $ShimFile --localkeys --yes
+      ./refind-install --shim $ShimFile --localkeys --yes

    else
    else

-      ./install.sh --shim $ShimFile --yes
+      ./refind-install --shim $ShimFile --yes

    fi
 else
    if [[ -n $SBSign && -n $OpenSSL ]] ; then
    fi
 else
    if [[ -n $SBSign && -n $OpenSSL ]] ; then

-      ./install.sh --localkeys --yes
+      ./refind-install --localkeys --yes

    else
    else

-      ./install.sh --yes
+      ./refind-install --yes

    fi
 fi
 
 # CAUTION: Don't create a %preun or a %postun script that deletes the files
    fi
 fi
 
 # CAUTION: Don't create a %preun or a %postun script that deletes the files

-# installed by install.sh, since that script will run after an update, thus
-# wiping out the just-updated files.
+# installed by refind-install, since that script will run after an update,
+# thus wiping out the just-updated files.

 
 %changelog
 * Sat Sep 19 2015 R Smith <rodsmith@rodsbooks.com> - 0.9.2
 
 %changelog
 * Sat Sep 19 2015 R Smith <rodsmith@rodsbooks.com> - 0.9.2