-0.9.3 (??/??/2015):
--------------------
+0.9.3 (11/8/2015):
+------------------
+
+- Fixed bug that caused refind-install to not unmount the ESP when it
+ should under OS X.
- Modified refind-install and mkrlconf scripts to use /proc/cmdline as
source for default boot options EXCEPT when refind-install receives the
--- /dev/null
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ width="420"
+ height="128"
+ id="svg12874"
+ version="1.1"
+ inkscape:version="0.48.4 r9939"
+ inkscape:export-filename="/home/rodsmith/programming/refind/current/images/banner-refind-white.png"
+ inkscape:export-xdpi="39.483315"
+ inkscape:export-ydpi="39.483315"
+ sodipodi:docname="banner-refind-06-color-allwhite-shadow.svg">
+ <defs
+ id="defs12876">
+ <filter
+ id="filter16789"
+ style="color-interpolation-filters:sRGB;"
+ inkscape:label="Drop Shadow">
+ <feFlood
+ id="feFlood16791"
+ flood-opacity="0.7"
+ flood-color="rgb(0,0,0)"
+ result="flood" />
+ <feComposite
+ id="feComposite16793"
+ in2="SourceGraphic"
+ in="flood"
+ operator="in"
+ result="composite1" />
+ <feGaussianBlur
+ id="feGaussianBlur16795"
+ in="composite"
+ stdDeviation="3"
+ result="blur" />
+ <feOffset
+ id="feOffset16797"
+ dx="3"
+ dy="3"
+ result="offset" />
+ <feComposite
+ id="feComposite16799"
+ in2="offset"
+ in="SourceGraphic"
+ operator="over"
+ result="composite2" />
+ </filter>
+ <filter
+ id="filter16801"
+ style="color-interpolation-filters:sRGB;"
+ inkscape:label="Drop Shadow">
+ <feFlood
+ id="feFlood16803"
+ flood-opacity="0.7"
+ flood-color="rgb(0,0,0)"
+ result="flood" />
+ <feComposite
+ id="feComposite16805"
+ in2="SourceGraphic"
+ in="flood"
+ operator="in"
+ result="composite1" />
+ <feGaussianBlur
+ id="feGaussianBlur16807"
+ in="composite"
+ stdDeviation="3"
+ result="blur" />
+ <feOffset
+ id="feOffset16809"
+ dx="3"
+ dy="3"
+ result="offset" />
+ <feComposite
+ id="feComposite16811"
+ in2="offset"
+ in="SourceGraphic"
+ operator="over"
+ result="composite2" />
+ </filter>
+ <filter
+ id="filter16813"
+ style="color-interpolation-filters:sRGB;"
+ inkscape:label="Drop Shadow">
+ <feFlood
+ id="feFlood16815"
+ flood-opacity="0.7"
+ flood-color="rgb(0,0,0)"
+ result="flood" />
+ <feComposite
+ id="feComposite16817"
+ in2="SourceGraphic"
+ in="flood"
+ operator="in"
+ result="composite1" />
+ <feGaussianBlur
+ id="feGaussianBlur16819"
+ in="composite"
+ stdDeviation="3"
+ result="blur" />
+ <feOffset
+ id="feOffset16821"
+ dx="3"
+ dy="3"
+ result="offset" />
+ <feComposite
+ id="feComposite16823"
+ in2="offset"
+ in="SourceGraphic"
+ operator="over"
+ result="composite2" />
+ </filter>
+ </defs>
+ <sodipodi:namedview
+ id="base"
+ pagecolor="#c0c0c0"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="1.3671875"
+ inkscape:cx="221.54507"
+ inkscape:cy="58.078242"
+ inkscape:current-layer="layer1"
+ showgrid="true"
+ inkscape:document-units="px"
+ inkscape:grid-bbox="true"
+ inkscape:window-width="1108"
+ inkscape:window-height="979"
+ inkscape:window-x="319"
+ inkscape:window-y="25"
+ inkscape:window-maximized="0" />
+ <metadata
+ id="metadata12879">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ <dc:title></dc:title>
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <g
+ id="layer1"
+ inkscape:label="Layer 1"
+ inkscape:groupmode="layer"
+ transform="translate(0,64)">
+ <g
+ id="g14396"
+ transform="translate(-3.0027063,-3.0672157)"
+ style="filter:url(#filter16789)">
+ <path
+ sodipodi:end="6.3137247"
+ sodipodi:start="0.038057173"
+ transform="matrix(0.92479648,0,0,1.0146143,3.6793308,-74.868835)"
+ d="m 114.23105,62.798281 a 7.0144992,5.8831286 0 1 1 0.002,-0.0442 l -7.01122,-0.179639 z"
+ sodipodi:ry="5.8831286"
+ sodipodi:rx="7.0144992"
+ sodipodi:cy="62.57444"
+ sodipodi:cx="107.22163"
+ id="path13770"
+ style="fill:#0000bc;fill-opacity:1;stroke:#0000bc;stroke-opacity:1"
+ sodipodi:type="arc" />
+ <path
+ inkscape:transform-center-y="-2.717824"
+ inkscape:transform-center-x="2.2822755"
+ transform="matrix(-0.36198059,-1.0983946,1.2009376,-0.52324781,92.632403,-15.195328)"
+ d="M 25.234285,15.542856 13.408625,14.102867 1.5350652,13.13418 8.6949622,3.6128532 15.47065,-6.1856079 20.136412,4.7757081 z"
+ inkscape:randomized="0"
+ inkscape:rounded="0"
+ inkscape:flatsided="false"
+ sodipodi:arg2="1.6720838"
+ sodipodi:arg1="0.62488624"
+ sodipodi:r2="6.6397543"
+ sodipodi:r1="13.753239"
+ sodipodi:cy="7.4971428"
+ sodipodi:cx="14.08"
+ sodipodi:sides="3"
+ id="path13768"
+ style="fill:#0000bc;fill-opacity:1;stroke:#0000bc;stroke-opacity:1"
+ sodipodi:type="star" />
+ <path
+ sodipodi:end="6.3137247"
+ sodipodi:start="0.038057173"
+ transform="matrix(1.0623728,0,0,1.0939231,-25.695042,-96.297006)"
+ d="m 128.90965,140.02735 a 6.4000001,6.1257143 0 1 1 0.002,-0.046 l -6.39702,-0.18705 z"
+ sodipodi:ry="6.1257143"
+ sodipodi:rx="6.4000001"
+ sodipodi:cy="139.79428"
+ sodipodi:cx="122.51428"
+ id="path13774"
+ style="fill:#0000bc;fill-opacity:1;stroke:#0000bc;stroke-opacity:1"
+ sodipodi:type="arc" />
+ <rect
+ transform="matrix(0.87626487,-0.48182972,0.50478347,0.86324599,0,0)"
+ y="62.893646"
+ x="54.812462"
+ height="36.635689"
+ width="13.590784"
+ id="rect13772"
+ style="fill:#0000bc;fill-opacity:1;stroke:#0000bc;stroke-width:0.97056359;stroke-opacity:1" />
+ <path
+ transform="translate(0,-64)"
+ inkscape:connector-curvature="0"
+ id="path14394"
+ d="M 62.24715,93.833652 C 44.041938,92.252582 28.546517,79.385025 23.734015,61.851955 22.501283,57.360822 22.301415,55.744916 22.29782,50.240526 22.294225,44.735665 22.524224,42.859657 23.75127,38.385327 28.007142,22.866603 41.06795,10.600982 56.852864,7.2990704 63.103797,5.9914908 69.776278,6.0487609 75.778578,7.4615104 83.004074,9.1621606 89.298831,12.39401 94.931372,17.294921 l 1.507079,1.311319 -4.873168,4.875923 -4.873169,4.875922 -1.296768,-1.097309 c -6.117882,-5.17688 -14.176954,-7.796403 -21.868196,-7.108048 -6.678051,0.597677 -12.12638,2.835457 -17.21195,7.069426 -8.343558,6.946394 -12.204448,18.453055 -9.850305,29.356991 1.730081,8.013399 6.921261,15.163838 14.115881,19.443507 4.268634,2.539167 8.875228,3.870069 14.059767,4.062041 7.738606,0.286543 14.749025,-2.096311 20.646607,-7.017823 5.644445,-4.710268 9.670531,-12.247325 10.415034,-19.497527 0.08051,-0.784007 0.193121,-1.47221 0.250249,-1.52934 0.13361,-0.133608 13.406277,0.33269 13.643537,0.479329 0.44025,0.27209 -0.49058,6.224421 -1.54774,9.897282 -2.3965,8.326113 -7.67389,16.284899 -14.40898,21.730061 -8.822615,7.132884 -20.238599,10.655628 -31.3921,9.686977 z"
+ style="fill:#0000bc;fill-opacity:1;stroke:#0000bc;stroke-width:0.18285714;stroke-opacity:1" />
+ </g>
+ <g
+ id="g16653"
+ transform="translate(1.4628571,-2.1942857)"
+ style="filter:url(#filter16801)">
+ <path
+ d="m 147.4908,-25.683422 0,-0.552 c 0,-3.311997 -1.472,-4.416 -4.14,-4.416 -3.67999,0 -5.612,1.748004 -6.256,5.796 l -5.704,34.6839995 c -0.092,0.5519995 -0.092,1.0120005 -0.092,1.4720005 0,3.035997 1.74801,4.876 4.876,4.876 3.496,0 5.428,-2.116005 6.164,-6.3480005 l 3.036,-17.664 c 1.288,-7.6359925 2.11601,-11.2240005 8.188,-11.8679995 2.3,-0.276 5.06001,0.275998 7.544,-1.288 1.748,-1.103999 2.76,-2.852003 2.76,-4.968 0,-3.311997 -1.932,-4.968 -5.796,-4.968 -4.13999,0 -7.636,1.748003 -10.58,5.244"
+ style="font-size:92px;font-style:italic;font-variant:normal;font-weight:bold;font-stretch:normal;text-align:center;line-height:125%;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;font-family:ITC Benguiat Gothic;-inkscape-font-specification:ITC Benguiat Gothic Bold Italic"
+ id="path16377"
+ inkscape:connector-curvature="0" />
+ <path
+ d="m 176.97393,4.8605775 3.68,-22.3559995 22.08,0 c 5.70399,0 8.28,-1.748005 8.28,-5.98 0,-3.127997 -1.84001,-4.416 -5.796,-4.416 l -22.816,0 1.38,-7.912 21.804,0 c 5.79599,0 8.648,-1.932005 8.648,-5.98 0,-3.495997 -1.93201,-4.784 -6.072,-4.784 l -25.944,0 c -6.44,0 -8.556,1.472005 -9.476,6.992 l -8.004,47.4719995 c -0.184,0.9199991 -0.184,1.6560008 -0.184,2.3920005 0,4.415995 2.944,5.612 8.832,5.612 l 24.84,0 c 5.05999,0 8.096,-2.576005 8.096,-6.6240005 0,-2.8519971 -2.02401,-4.416 -5.888,-4.416 l -23.46,0"
+ style="font-size:92px;font-style:italic;font-variant:normal;font-weight:bold;font-stretch:normal;text-align:center;line-height:125%;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:middle;fill:#0000bc;fill-opacity:1;stroke:none;font-family:ITC Benguiat Gothic;-inkscape-font-specification:ITC Benguiat Gothic Bold Italic"
+ id="path16379"
+ inkscape:connector-curvature="0" />
+ <path
+ d="m 232.22424,-17.495422 18.032,0 c 5.704,0 8.372,-1.748005 8.372,-5.98 0,-3.127997 -1.932,-4.416 -5.888,-4.416 l -18.768,0 1.38,-7.912 18.216,0 c 5.79599,0 8.74,-1.932005 8.74,-5.98 0,-3.495997 -1.932,-4.784 -6.072,-4.784 l -22.448,0 c -6.43999,0 -8.556,1.472005 -9.476,6.992 l -8.28,48.8519995 c -0.092,0.6439994 -0.184,1.1960005 -0.184,1.7480005 0,3.311996 1.84,5.06 5.244,5.06 4.048,0 5.796,-2.208005 6.624,-6.8080005 l 4.508,-26.7719995"
+ style="font-size:92px;font-style:italic;font-variant:normal;font-weight:bold;font-stretch:normal;text-align:center;line-height:125%;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:middle;fill:#0000bc;fill-opacity:1;stroke:none;font-family:ITC Benguiat Gothic;-inkscape-font-specification:ITC Benguiat Gothic Bold Italic"
+ id="path16381"
+ inkscape:connector-curvature="0" />
+ <path
+ d="m 264.01312,9.2765775 c -0.092,0.6439994 -0.184,1.2880005 -0.184,1.8400005 0,3.219996 1.748,4.968 4.876,4.968 4.41599,0 6.164,-2.024005 6.992,-6.8080005 l 8.464,-50.0479995 c 0.092,-0.46 0.092,-0.920001 0.092,-1.38 0,-2.943998 -1.84001,-4.692 -5.244,-4.692 -3.68,0 -5.98,2.116004 -6.624,6.072 l -8.372,50.0479995"
+ style="font-size:92px;font-style:italic;font-variant:normal;font-weight:bold;font-stretch:normal;text-align:center;line-height:125%;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:middle;fill:#0000bc;fill-opacity:1;stroke:none;font-family:ITC Benguiat Gothic;-inkscape-font-specification:ITC Benguiat Gothic Bold Italic"
+ id="path16383"
+ inkscape:connector-curvature="0" />
+ <path
+ d="m 304.19555,-25.407422 c 0.092,-0.368 0.092,-0.736001 0.092,-1.012 0,-2.759998 -1.748,-4.324 -4.692,-4.324 -3.95599,0 -5.98,1.748004 -6.624,5.888 l -5.796,34.6839995 c -0.092,0.5519995 -0.092,1.0120005 -0.092,1.4720005 0,3.035997 1.84001,4.876 4.968,4.876 3.496,0 5.428,-2.116005 6.164,-6.3480005 l 3.22,-18.952 c 1.288,-7.5439925 5.79601,-11.8679995 12.144,-11.8679995 4.508,0 6.716,2.116004 6.716,6.256 0,0.827999 -0.092,2.392002 -0.46,4.508 l -3.22,20.0559995 c -0.092,0.4599995 -0.092,0.9200005 -0.092,1.3800005 0,2.943997 1.93201,4.876 5.152,4.876 3.404,0 5.428,-2.024005 6.164,-6.2560005 l 3.68,-21.9879995 c 0.276,-1.839999 0.368,-3.680002 0.368,-5.52 0,-7.911993 -5.52001,-13.156 -13.984,-13.156 -4.69199,0 -9.108,1.840003 -13.708,5.428"
+ style="font-size:92px;font-style:italic;font-variant:normal;font-weight:bold;font-stretch:normal;text-align:center;line-height:125%;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;font-family:ITC Benguiat Gothic;-inkscape-font-specification:ITC Benguiat Gothic Bold Italic"
+ id="path16385"
+ inkscape:connector-curvature="0" />
+ <path
+ d="m 372.51418,-20.531422 -4.232,25.8519995 c -2.668,0.1839999 -4.784,0.184 -6.348,0.184 -8.09599,0 -11.776,-1.8400057 -11.776,-7.544 0,-10.1199895 8.46401,-18.1240005 22.356,-18.4919995 m 1.656,-9.844 -0.736,0 c -8.73999,0 -15.82401,1.656003 -21.068,4.968 -8.83199,5.519994 -14.26,15.088009 -14.26,24.47199955 0,5.97999405 2.392,10.94800345 6.808,13.98400045 3.40399,2.299997 8.64801,2.852 16.1,2.852 l 11.684,0 c 3.31199,0 5.244,-1.840004 5.888,-5.52 l 8.832,-52.624 c 0.092,-0.552 0.092,-1.012001 0.092,-1.472 0,-2.851998 -1.748,-4.416 -4.968,-4.416 -3.312,0 -5.52,1.932003 -6.164,5.428 l -2.208,12.328"
+ style="font-size:92px;font-style:italic;font-variant:normal;font-weight:bold;font-stretch:normal;text-align:center;line-height:125%;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;font-family:ITC Benguiat Gothic;-inkscape-font-specification:ITC Benguiat Gothic Bold Italic"
+ id="path16387"
+ inkscape:connector-curvature="0" />
+ </g>
+ <text
+ xml:space="preserve"
+ style="font-size:36px;font-style:italic;font-variant:normal;font-weight:600;font-stretch:normal;text-align:center;line-height:125%;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:middle;fill:#ff0000;fill-opacity:1;stroke:none;font-family:BouganSSi;-inkscape-font-specification:BouganSSi Semi-Bold Italic;filter:url(#filter16813)"
+ x="260.42313"
+ y="49.695934"
+ id="text16353"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan16355"
+ x="260.42313"
+ y="49.695934">Boot Management</tspan></text>
+ </g>
+</svg>
+refind (0.10.0-0ppa1) trusty; urgency=medium
+
+ * Version bump
+
+ -- Roderick Smith <rodsmith@rodsbooks.com> Sun, 08 Nov 2015 16:53:35 -0500
+
refind (0.9.2-0ppa1) trusty; urgency=medium
* Version bump
# Copy documentation to /usr/share/doc/refind
mkdir -p $BUILD_ROOT/usr/share/doc/refind
-cp -a docs/* $BUILD_ROOT/usr/share/doc/refind/
+cp -a docs/Styles $BUILD_ROOT/usr/share/doc/refind/
+cp -a docs/refind $BUILD_ROOT/usr/share/doc/refind/
install -Dp -m0644 NEWS.txt COPYING.txt LICENSE.txt README.txt CREDITS.txt $BUILD_ROOT/usr/share/doc/refind
+# Copy man pages to /usr/share/man/man8
+mkdir -p $BUILD_ROOT/usr/share/man/man8
+install -Dp -m0644 docs/man/mvrefind.8 $BUILD_ROOT/usr/share/man/man8
+install -Dp -m0644 docs/man/mkrlconf.8 $BUILD_ROOT/usr/share/man/man8
+
# Copy keys to /etc/refind.d/keys
mkdir -p $BUILD_ROOT/etc/refind.d/keys
install -Dp -m0644 keys/* $BUILD_ROOT/etc/refind.d/keys
--- /dev/null
+.\" Copyright 2015 Roderick W. Smith (rodsmith@rodsbooks.com)
+.\" May be distributed under the GNU General Public License version 3 or
+any later version
+.TH "MKRLCONF" "8" "0.10.0" "Roderick W. Smith" "rEFInd Manual"
+.SH "NAME"
+mkrlconf \- Create a Linux kernel configuration file for rEFInd
+.SH "SYNOPSIS"
+.BI "mkrlconf "
+[ \-\-force ]
+
+.SH "DESCRIPTION"
+
+To boot a Linux kernel directly, rEFInd must normally pass system-specific
+parameters to help the kernel locate its initial RAM disk (initrd) file,
+the installation's root filesystem, and so on. rEFInd stores this
+information in a file called \fIrefind_linux.conf\fR, which is stored in
+the same directory as the kernel(s) to which it applies. The \fImkrlconf\fR
+script creates this configuration file in \fI/boot\fR, using the current
+boot options (from \fI/proc/cmdline\fR) to populate
+\fI/boot/refind_linux.conf\fR with boot options that are probably (but not
+certainly) correct.
+
+The file created in this way has three lines, which correspond to three
+entries on the rEFInd suboptions menu. The first entry boots using the
+options found in \fI/proc/cmdline\fR. The second entry boots using the same
+options as the first, but with \fBsingle\fR added. The third entry boots
+with minimal options of \fBro root={CURRENT_ROOT_DEVICE}\fR, where
+\fB{CURRENT_ROOT_DEVICE}\fR identifies the current root (\fI/\fR)
+filesystem. Users may manually edit the \fIrefind_linux.conf\fR file to
+suit their needs, of course.
+
+.SH "OPTIONS"
+
+.TP
+.B \-\-force
+Ordinarily, if \fImkrlconf\fR finds an existing
+\fI/boot/refind_linux.conf\fR file, it refuses to replace it. The
+\fB\-\-force\fR option causes \fImkrlconf\fR to replace the existing file
+in favor of one it generates.
+
+.SH "AUTHORS"
+Primary author: Roderick W. Smith (rodsmith@rodsbooks.com)
+
+.SH "SEE ALSO"
+\fBmvrefind (8)\fR
+
+\fIhttp://www.rodsbooks.com/refind/\fR
+
+.SH "AVAILABILITY"
+The \fBmkrlconf\fR command is part of the \fIrEFInd\fR package and is
+available from Roderick W. Smith.
--- /dev/null
+.\" Copyright 2015 Roderick W. Smith (rodsmith@rodsbooks.com)
+.\" May be distributed under the GNU General Public License version 3 or
+any later version
+.TH "MVREFIND" "8" "0.10.0" "Roderick W. Smith" "rEFInd Manual"
+.SH "NAME"
+mvrefind \- Move a rEFInd installation from one location to another
+.SH "SYNOPSIS"
+.BI "mvrefind \fISOURCE DEST\fR"
+
+.SH "DESCRIPTION"
+
+Move a rEFInd installation from \fISOURCE\fR to \fIDEST\fR, where both
+\fISOURCE\fR and \fIDEST\fR are directories on the EFI System Partition
+(ESP), with \fISOURCE\fR containing a working rEFInd installation. This
+operation entails taking several actions:
+
+.TP
+.B *
+Renaming the \fISOURCE\fR directory to \fIDEST\fR.
+
+.TP
+.B *
+Renaming the rEFInd binary to a suitable value given the new destination.
+For instance, if \fIDEST\fR is EFI/BOOT on the EFI System Partition (ESP),
+the rEFInd binary should be \fIbootx64.efi\fR (or something similar but
+with a different architecture code).
+
+.TP
+.B *
+Altering the computer's NVRAM entries to point to rEFInd at its new
+location.
+
+.TP
+.B *
+If Shim is detected, renaming operations and NVRAM entry pointers are
+adjusted appropriately.
+
+.TP
+.B *
+If the \fIDEST\fR exists, its contents are preserved.
+
+.PP
+
+Broadly speaking, \fImvrefind\fR understands three types of locations for
+both \fISOURCE\fR and \fIDEST\fR, relative to the root of the ESP:
+
+.TP
+.B *
+\fBEFI/BOOT\fR -- The \fIbootx64.efi\fR (or similar for other
+architectures) filename in this location is the "fallback filename," which
+is used by removable boot media and as a boot loader of last resort on hard
+disks. Some EFIs can't remember their normal boot entries, and on them,
+rEFInd must be installed here (or as the Windows boot loader). When this
+directory is the \fIDEST\fR and it already exists, the existing
+\fIEFI/BOOT\fR is backed up to \fIEFI/BOOT\-rEFIndBackup\fR; and if the
+\fISOURCE\fR is \fIEFI/BOOT\fR and \fIEFI/BOOT\-rEFIndBackup\fR exists, it
+is renamed to \fIEFI/BOOT\fR after rEFInd is moved to its destination.
+
+.TP
+.B *
+\fBEFI/Microsoft/boot\fR -- The \fIbootmgfw.efi\fR file in this location
+normally holds the Windows boot loader. Machines with broken EFIs may
+refuse to accept or remember proper boot entries and will instead boot this
+entry in preference to all others. In such cases, using rEFInd requires
+moving the Microsoft boot loader elsewhere and replacing it with rEFInd.
+When this directory is the \fIDEST\fR, \fImvrefind\fR moves the original
+\fIbootmgfw.efi\fR file down one level (to \fIEFI/Microsoft\fR) and stores
+\fIrefind_x64.efi\fR (or Shim) in that location. When moving from
+\fIEFI/Microsoft/boot\fR, this process is reversed.
+
+.TP
+.B *
+\fBAnything else\fR -- Any other \fISOURCE\fR or \fIDEST\fR location is
+treated as a regular rEFInd installation, with a proper NVRAM entry created
+by \fIefibootmgr\fR.
+
+.PP
+
+\fImvrefind\fR attempts to identify the ESP and refuses to move between the
+ESP and any other partition. When it does move files, it moves the main
+rEFInd binary, the \fIrefind.conf\fR file, any identified Shim binary, and
+the \fIicons\fR, \fIicons\-backup\fR, \fIdrivers_*\fR, and \fIkeys\fR
+subdirectories. If other rEFInd files or directories are present in
+\fISOURCE\fR (such as a custom theme/icons directory), they will not be
+moved. If \fISOURCE\fR is empty after the specified files and
+subdirectories are moved, \fISOURCE\fR will be deleted.
+
+.SH "AUTHORS"
+Primary author: Roderick W. Smith (rodsmith@rodsbooks.com)
+
+.SH "SEE ALSO"
+\fBmkrlconf (8)\fR
+
+\fIhttp://www.rodsbooks.com/refind/\fR
+
+.SH "AVAILABILITY"
+The \fBmvrefind\fR command is part of the \fIrEFInd\fR package and is
+available from Roderick W. Smith.
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>\r
\r
<p>Originally written: 3/14/2012; last Web page update:\r
-9/19/2015, referencing rEFInd 0.9.2</p>\r
+11/8/2015, referencing rEFInd 0.10.0</p>\r
\r
\r
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>\r
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-11/1/2015, referencing rEFInd 0.9.3</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<div style="float:right; width:55%">
-<p>Many casual users will be able to use rEFInd without making changes to its settings; in its default configuration, the boot manager automatically detects all the EFI boot loader programs you have on your EFI System Partition (ESP) (or your OS X boot partition, in the case of Macs) and displays icons for them. On Macs, rEFInd also presents legacy BIOS boot options by default. Sometimes, though, you may want to tweak rEFInd's configuration. Sometimes you can obtain your desired results by adjusting the filenames of your boot loaders. Other times, you can edit rEFInd's configuration file, <tt>refind.conf</tt>, which resides in the same directory as its binary file (<tt>refind_x64.efi</tt> or whatever you've renamed it).</p>
+<p>Many casual users will be able to use rEFInd without making changes to its settings; in its default configuration, the boot manager automatically detects all the EFI boot loader programs you have on your EFI System Partition (ESP) (or your OS X boot partition, in the case of Macs) in conventional locations and displays icons for them. On Macs, rEFInd also presents legacy BIOS boot options by default. Sometimes, though, you may want to tweak rEFInd's configuration. Sometimes you can obtain your desired results by adjusting the filenames of your boot loaders. Other times, you can edit rEFInd's configuration file, <tt>refind.conf</tt>, which resides in the same directory as its binary file (<tt>refind_x64.efi</tt> or whatever you've renamed it).</p>
</div>
<td>On some Macs, this option causes rEFInd to tell the firmware that the specified version of OS X is being launched, even when another OS is selected. The effect is that the firmware may initialize hardware differently, which may have beneficial (or detrimental) results. If your Mac's video output isn't working normally, this option may help. On the other hand, keyboards and mice are known to sometimes stop functioning if this option is used, so you shouldn't use it unnecessarily. This option has no effect on non-Apple hardware. The default is to not use this feature.</td>
</tr>
<tr>
- <td><tt>csr_rotate</tt></td>
+ <td><tt>csr_values</tt></td>
<td>List of hexadecimal values</td>
- <td>Specifies values that may be set via the <tt>csr_rotate</tt> tool for Apple's System Integrity Protection (SIP). SIP stores values in NVRAM to set restrictions on what users (even <tt>root</tt>) may do in
recent versions of OS X. If you want to be able to control these restrictions in rEFInd, you must set the values you want to use here <i>and</i> set <tt>csr_rotate</tt> on the <tt>showtools</tt> line (which must also be uncommented). Note that values are specified in hexadecimal, with no leading <tt>0x</tt> or other hexadecimal indicator. SIP is described in more detail on many Web sites, such as <a href="http://osxarena.com/2015/10/guide-details-apples-system-integrity-protection-sip-for-hackintosh/">here</a> and <a href="http://www.idelta.info/archives/sip-rootless-internal-in-el-capitan/">here.</a></td>
+ <td>Specifies values that may be set via the <tt>csr_rotate</tt> tool for Apple's System Integrity Protection (SIP). SIP stores values in NVRAM to set restrictions on what users (even <tt>root</tt>) may do in
OS X 10.11. If you want to be able to control these restrictions in rEFInd, you must set the values you want to use here <i>and</i> set <tt>csr_rotate</tt> on the <tt>showtools</tt> line (which must also be uncommented). Note that values are specified in hexadecimal, with no leading <tt>0x</tt> or other hexadecimal indicator. SIP is described in more detail on many Web sites, such as <a href="http://osxarena.com/2015/10/guide-details-apples-system-integrity-protection-sip-for-hackintosh/">here</a> and <a href="http://www.idelta.info/archives/sip-rootless-internal-in-el-capitan/">here.</a></td>
</tr>
<tr>
<td><tt>include</tt></td>
</tr>
</table>
-<p>Prior to version 0.2.4, rEFInd supported a token called <tt>disable</tt>, whose function partially overlapped with <tt>hideui</tt>. Version 0.2.4 merges many of the features of these two tokens into <tt>hideui</tt> and creates the new <tt>showtools</tt> option, which provides the remaining functionality in a more flexible way.</p>
-
<p>As an example of rEFInd configuration, consider the following <tt>refind.conf</tt> file:</p>
<pre class="listing">
<p>As an example, consider the following entries:</p>
<pre class="listing">
-menuentry "Ubuntu Linux" {
+menuentry "Ubuntu" {
loader /EFI/ubuntu/grubx64.efi
disabled
}
}
</pre>
-<p>This example sets up three entries: one for Ubuntu Linux, one for Arch Linux, and one to launch a shell script. Note that the final entry uses different directory separators from the first two, simply to demonstrate the fact that it's possible. (The form of directory separators in <tt>options</tt> lines is important, though, because the program being launched may expect a particular directory separator character.) The Ubuntu entry sets no icon, since rEFInd will note that the boot loader is stored in the <tt>ubuntu</tt> directory, and it will automatically find the appropriate Ubuntu icon (<tt>os_ubuntu.png</tt>). This option is, however, disabled, so no matching icon will appear when you reboot unless you first comment out or delete the <tt>disabled</tt> line.</p>
+<p>This example sets up three entries: one for Ubuntu, one for Arch Linux, and one to launch a shell script. Note that the final entry uses different directory separators from the first two, simply to demonstrate the fact that it's possible. (The form of directory separators in <tt>options</tt> lines is important, though, because the program being launched may expect a particular directory separator character.) The Ubuntu entry sets no icon, since rEFInd will note that the boot loader is stored in the <tt>ubuntu</tt> directory, and it will automatically find the appropriate Ubuntu icon (<tt>os_ubuntu.png</tt>). This entire entry is, however, disabled, so no matching icon will appear when you reboot unless you first comment out or delete the <tt>disabled</tt> line.</p>
<p class="sidebar"><b>Tip:</b> Under Linux, you can learn a filesystem's label by using <tt>blkid</tt>, as in <tt class="userinput">blkid /dev/sda1</tt>. The filesystem's label, if set, is identified by the keyword <tt>LABEL</tt> in the output. Some versions also return the partition's label and partition GUID (referred to as <tt>PARTUUID</tt> by <tt>blkid</tt>). You can obtain the partition's name and unique GUID using <tt>sgdisk</tt>, as in <tt class="userinput">sgdisk -i 1 /dev/sda</tt> to find the data on <tt>/dev/sda1</tt>.</p>
<h2>Adjusting the Default Boot Option</h2>
</a>
-<p>Just before launching an OS, rEFInd stores the description in the EFI variable <tt>PreviousBoot</tt> with a GUID of 36d08fa7-cf0b-42f5-8f14-68df73ed3740. The next time it launches, it reads that same variable and sets the default boot loader to that value, if it's still available and if the first item in <tt>default_selection</tt> in the <tt>refind.conf</tt> file is a plus sign (<tt>+</tt>).</p>
+<p>Just before launching an OS, rEFInd stores the description in the EFI variable <tt>PreviousBoot</tt> with a GUID of 36d08fa7-cf0b-42f5-8f14-68df73ed3740. The next time rEFInd launches, it reads that same variable and sets the default boot loader to that value, if it's still available and if the first item in <tt>default_selection</tt> in the <tt>refind.conf</tt> file is a plus sign (<tt>+</tt>).</p>
<p>Under Linux, the variable that rEFInd uses to store this information is accessible as <tt>/sys/firmware/efi/efivars/PreviousBoot-36d08fa7-cf0b-42f5-8f14-68df73ed3740</tt>. Thus, you can back up this value, modify it, and write it back out to adjust your next-booted OS. Getting this string just right can be a bit tricky, though, and if the kernel doesn't like its format, it will not let you modify the variable. If you try to modify the variable, be aware that it's stored in UTF-16 format. As with the <tt>default_selection</tt> token in <tt>refind.conf</tt>, you can enter any substring that uniquely identifies the entry you want to boot.</p>
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 4/19/2012; last Web page update:
-9/19/2015, referencing rEFInd 0.9.2</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<tt>refind_linux.conf</tt> file. Without the first of these options,
rEFInd could not locate my kernel; and without the second, the boot
failed with a message to the effect that the initial RAM disk could not
- find <tt>/sbin/init</tt>.</li>
+ find <tt>/sbin/init</tt>. rEFInd 0.10.0 adds <tt>@/boot</tt> as a
+ standard option to <tt>also_scan_dirs</tt>, and its
+ <tt>refind-install</tt> and <tt>mkrlconf</tt> scripts should pick up
+ the root flags, assuming the system is booted into the regular
+ installation. These additions make it easier to set up rEFInd to work
+ with Btrfs.</li>
<li><b>ISO-9660</b>—This driver originated with rEFIt's author, but
he never released a final version. Its code was improved by Oracle for
one can be helpful; however, you may need to install it on your hard
disk before you can read an optical disc.</li>
-<li><b>HFS+</b>—Oracle seems to have written this driver, apparently
- with some code taken from open source Apple examples. It was then
- further modified by the Clover authors. I expect this driver to have
- limited appeal to most rEFInd users. Macs don't need it, since Apple's EFI
- implementation provides its own HFS+ driver, and HFS+ isn't normally
- used on UEFI-based PCs. Some CDs are mastered with both ISO-9660 and
- HFS+, or even with HFS+ alone, and it's conceivable that an HFS+ driver
- would be useful when accessing such discs. I'm providing the driver
- mainly because it compiled cleanly with no extra work, aside from
- providing a Makefile entry for it.</li>
+<li><b>HFS+</b>—Oracle wrote this driver, apparently with some code
+ taken from open source Apple examples. It was then further modified by
+ the Clover authors. I expect this driver to have limited appeal to most
+ rEFInd users. Macs don't need it, since Apple's EFI implementation
+ provides its own HFS+ driver, and HFS+ isn't normally used on
+ UEFI-based PCs. Some CDs are mastered with both ISO-9660 and HFS+, or
+ even with HFS+ alone, and it's conceivable that an HFS+ driver would be
+ useful when accessing such discs. Also, one unusual feature of this
+ driver is that it can read files from within an Apple LVM setup, which
+ Apple's own EFI HFS+ driver can't do. The upshot of this feature is
+ that if you load this driver on a Mac that uses Apple's LVM, rEFInd is
+ likely to show two OS X boot options. Ordinarily this is pointless, but
+ it could be helpful if your Recovery HD volume becomes damaged. I'm
+ providing the driver mainly because it compiled cleanly with no extra
+ work, aside from providing a Makefile entry for it.</li>
<p class="sidebar"><b>Warning:</b> I've received multiple reports of system hangs when using the NTFS driver; however, I've been unable to replicate the problem. (The problem is probably triggered either by interactions with specific EFIs or by unique features of the "problem" NTFS volumes.) I therefore recommend avoiding it unless it's absolutely necessary. I've added a couple of checks to the driver code in rEFInd 0.9.1 that <i>may</i> fix this problem, but these checks may also have no effect.</p>
<p>When you reboot after installing drivers, rEFInd should automatically detect and use the drivers you install. There's likely to be an extra delay, typically from one to five seconds, as rEFInd loads the drivers and tells the EFI to detect the filesystems they handle. For this reason, and because of the possibility of drivers harboring bugs, I recommend installing only those drivers that you need. If you like, you can install drivers you don't plan on using to some other directory, such as <tt>/drivers</tt> on the ESP's root. You can then load these drivers manually with the EFI shell's <tt>load</tt> command if the need arises in the future. You can then tell the shell to re-assign drive identifiers with <tt>map -r</tt>:</p>
<pre class="listing">
-fs0: <tt class="userinput">load reiserfs_x64.efi</tt>
+fs0: <tt class="userinput">load btrfs_x64.efi</tt>
fs0: <tt class="userinput">map -r</tt>
</pre>
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-9/19/2015, referencing rEFInd 0.9.2</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<li>The ability to set the VMX bit on certain Intel CPUs. This feature is necessary for certain virtualization tools, such as Hyper-V, and not all EFIs enable users to set it.</li>
+<li>Beginning with version 0.10.0, the ability to spoof the booting of OS X when booting non-Apple OSes. This changes the way a Mac's EFI initializes hardware, which can get secondary video chipsets working on some Macs. This feature is controlled via the <tt>spoof_osx_version</tt> token in <tt>refind.conf</tt>.</li>
+
+<li>Beginning with version 0.10.0, the ability to adjust Apple System Integrity Protection (SIP; aka "rootless" or "CSR") settings. These settings control what features are off-limits even to <tt>root</tt> in OS X 10.11 (El Capitan) and later. To use this feature, you must set specific CSR values on <tt>refind.conf</tt>'s <tt>csr_values</tt> line <i>and</i> add <tt>csr_rotate</tt> to the <tt>showtools</tt> line.</li>
+
</ul>
<p>On the flip side, at least for Mac users, rEFInd comes with less sophisticated Mac installation tools than does rEFIt, in favor of more OS-agnostic packaging.</p>
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-9/19/2015, referencing rEFInd 0.9.2</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<ul>
<li><b><a
- href="http://sourceforge.net/projects/refind/files/0.9.2/refind-bin-0.9.2.zip/download">A
+ href="http://sourceforge.net/projects/refind/files/0.10.0/refind-bin-0.10.0.zip/download">A
binary zip file</a></b>—Download this if you want to install
rEFInd and/or its filesystem drivers on an <i>x</i>86 or <i>x</i>86-64
computer and have no need to test rEFInd first by booting it on an
href="installing.html">Installing rEFInd</a> page. Some users of Arch
Linux have reported problems booting some specific Arch Linux kernels
with rEFInd and some other tools. For them, a <a
- href="http://sourceforge.net/projects/refind/files/0.9.2/refind-bin-gnuefi-0.9.2.zip/download">variant
+ href="http://sourceforge.net/projects/refind/files/0.10.0/refind-bin-gnuefi-0.10.0.zip/download">variant
package</a> exists in which the <i>x</i>86-64 binary was compiled with
GNU-EFI rather than the usual TianoCore EDK2. This change helps some
users with this problem.</li>
<li><b><a
- href="http://sourceforge.net/projects/refind/files/0.9.2/refind-0.9.2-1.x86_64.rpm/download">A
+ href="http://sourceforge.net/projects/refind/files/0.10.0/refind-0.10.0-1.x86_64.rpm/download">A
binary RPM file</a></b>—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
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
+ href="http://sourceforge.net/projects/refind/files/0.10.0/refind-0.10.0-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
files.</li>
<li><b><a
- href="http://sourceforge.net/projects/refind/files/0.9.2/refind_0.9.2-1_amd64.deb/download">A
+ href="http://sourceforge.net/projects/refind/files/0.10.0/refind_0.10.0-1_amd64.deb/download">A
binary Debian package</a></b>—If you use an <i>x</i>86-64 version
of Debian, Ubuntu, Mint, or another Debian-based distribution, you can
install from this package, which was converted from the binary RPM
<p class="sidebar"><b>Note:</b> At the moment, neither the bootable CD-R image file nor the bootable USB flash drive image file supports booting with Secure Boot active. The x86-64 version of the <a href="http://en.altlinux.org/Rescue">ALT Linux Rescue disc</a> uses a Secure Boot-enabled rEFInd, though, so you may find that useful in some situations.</p>
<li><b><a
- href="http://sourceforge.net/projects/refind/files/0.9.2/refind-cd-0.9.2.zip/download">A
+ href="http://sourceforge.net/projects/refind/files/0.10.0/refind-cd-0.10.0.zip/download">A
CD-R image file</a></b>—This download contains the same files as
the binary zip file, but you can burn it to a CD-R to test rEFInd
(and its filesystem drivers) without installing it first. (It boots on
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
+ href="http://sourceforge.net/projects/refind/files/0.10.0/refind-flashdrive-0.10.0.zip/download">A
USB flash drive image file</a></b>—Although you can create
your own rEFInd USB flash drive, you may find it easier to download
this version and copy it to your USB drive with <tt>dd</tt> or some
other low-level disk copying utility.</li>
<li><b><a
- href="http://sourceforge.net/projects/refind/files/0.9.2/refind-src-0.9.2.zip/download">A
- source code zip file</a></b>—This is useful if you want to compile
+ href="http://sourceforge.net/projects/refind/files/0.10.0/refind-src-0.10.0.tar.gz/download">A
+ source code tarball</a></b>—This is useful if you want to compile
the software locally. Note that I use Linux with the <a
href="https://sourceforge.net/projects/tianocore/">TianoCore EFI
Development Kit 2 (EDK2)</a> to build my binary packages (above),
- although the <a href="http://sourceforge.net/projects/gnu-efi">GNU-EFI</a>
- development tools are also supported.</li>
+ although the <a
+ href="http://sourceforge.net/projects/gnu-efi">GNU-EFI</a> development
+ tools are also supported, and are used in building the Ubuntu PPA.</li>
<li><b><a href="https://sourceforge.net/p/refind/code">Source code via
git</a></b>—If you want to peruse the source code in your Web
browser or get the very latest version (including pre-release bug fixes
and updates), you can use the Sourceforge git repository. This access
method is most useful to programmers, or at least to those who are
- familiar with programming tools. Note that if you need to ask "what's
- git?", this is probably not the best way for you to obtain rEFInd.</li>
+ familiar with programming tools. If you need to ask "what's git?", this
+ is probably not the best way for you to obtain rEFInd.</li>
</ul>
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-11/1/2015, referencing rEFInd 0.9.3</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<p>Subsequent sections of this document are on separate pages. Be aware that you probably don't need to read them all; just skip to the sections that interest you:</p>
+<p><b>Note:</b> I consider rEFInd to be <i>beta-quality software!</i> That said, rEFInd is a usable program in its current form on many systems. If you have problems, feel free to drop me a line.</p>
+
</div>
<div class="navbar">
</div>
-<p><b>Note:</b> I consider rEFInd to be <i>beta-quality software!</i> That said, rEFInd is a usable program in its current form on many systems. If you have problems, feel free to drop me a line.</p>
-
<a name="references">
<h2>References and Additional Information</h2>
</a>
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-9/19/2015, referencing rEFInd 0.9.2</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<p>I provide RPM and Debian package files for rEFInd; and starting with version 0.8.1, I'm maintaining an Ubuntu PPA for rEFInd. If you have a working RPM-based or Debian-based Linux installation that boots in EFI mode, using one of these files is likely to be the easiest way to install rEFInd: You need only download the file and issue an appropriate installation command. In some cases, double-clicking the package in your file manager will install it. If that doesn't work, a command like the following will install the RPM on an RPM-based system:</p>
-<pre class="listing"># <tt class="userinput">rpm -Uvh refind-0.9.2-1.x86_64.rpm</tt></pre>
+<pre class="listing"># <tt class="userinput">rpm -Uvh refind-0.10.0-1.x86_64.rpm</tt></pre>
<p>On a Debian-based system, the equivalent command is:</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.10.0-1_amd64.deb</tt></pre>
<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="installsh">
<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>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 class="sidebar"><b>Note:</b> If you're using a Macintosh, it's best to install rEFInd from OS X, if possible. In the past, the Mac's firmware was quirky enough that the Linux tools didn't always work reliably. The matter seems to have improved with recent versions of Linux tools, but I can't guarantee success if you use Linux for this task. There is one significant issue with OS X 10.11, though (see the next Warning sidebar).</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>
<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>—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 class="sidebar"><b>Warning:</b> OS X 10.11 ("El Capitan") implements a new feature called System Integrity Protection (SIP; aka "rootless" or "CSR"). When enabled, SIP prevents the final step of rEFInd installation—registering the boot loader with the firmware. Thus, to install rEFInd, you must either disable SIP or perform the installation from something other than your regular OS X installation. The <a href="sip.html">rEFInd and System Integrity Protection</a> page of this document describes the options.</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>
/dev/sda1 191284 16604 174681 9% /boot/efi
</pre>
-<p class="sidebar"><b>Warning:</b> If you're running Linux on a Mac, I recommend you install rEFInd under OS X. The Mac's boot process deviates a bit from EFI standards, so you'll probably have to use a tool called <tt>bless</tt> under Mac OS to do the job. Alternatively, there's a new Linux program, <tt>hfs-bless</tt>, part of the <a href="http://www.codon.org.uk/~mjg59/mactel-boot/"><tt>mactel-boot</tt></a> RPM package or as part of the <a href="https://launchpad.net/~detly/+archive/ubuntu/mactel-utils">mactel-utils PPA for Ubuntu</a>, that's supposed to work with <tt>efibootmgr</tt> to make a Mac HFS partition bootable. I've not yet tried it, though. There are also reports that the <tt>efibootmgr</tt> tool used under Linux can corrupt some Macs' firmware. Although I've seen some vague suggestions that this problem has been fixed under 3.<i>x</i> kernels, I haven't tested this claim.</p>
+<p class="sidebar"><b>Note:</b> If you're running Linux on a Mac, I recommend you install rEFInd under OS X. The Mac's boot process deviates a bit from EFI standards, and older versions of <tt>efibootmgr</tt> didn't always work properly on Macs. This problem seems to have gone away with more recent versions of <tt>efibootmgr</tt>, but using OS X may still be more reliable. On the other hand, Apple's new (as of OS X 10.11) System Integrity Protection (SIP) feature blocks the use of <tt>bless</tt> under OS X and so prevents rEFInd installation. The <a href="sip.html">rEFInd and System Integrity Protection</a> page of this document covers how to overcome SIP and install rEFInd. One of these methods is to do the job from Linux.</p>
<p>This example shows that <tt>/dev/sda1</tt> is mounted at <tt>/boot/efi</tt>, which is a typical configuration. (The ESP can be on another disk or partition, but <tt>/dev/sda1</tt> is the most common place for an ESP.) If your output shows <tt>/boot</tt> or <tt>/</tt> under the <tt>Mounted on</tt> column, then your ESP isn't mounted. (An exception is if you're mounting the ESP at <tt>/boot</tt>. This is an unusual configuration. If you're using it, you can proceed, making suitable adjustments to subsequent commands.) If you get a <tt>df: `/boot/efi': No such file or directory</tt> error message, then the <tt>/boot/efi</tt> directory doesn't even exist. In such cases, you may need to jump through some extra hoops, as described on my <a href="http://www.rodsbooks.com/efi-bootloaders/installation.html">EFI Boot Loader Installation</a> page.</p>
<h3>Installing rEFInd Manually Using Mac OS X</h3>
</a>
-<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>—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 class="sidebar"><b>Warning:</b> OS X 10.11 ("El Capitan") implements a new feature called System Integrity Protection (SIP; aka "rootless" or "CSR"). When enabled, SIP prevents the final step of rEFInd installation—registering the boot loader with the firmware. Thus, to install rEFInd, you must either disable SIP or perform the installation from something other than your regular OS X installation. The <a href="sip.html">rEFInd and System Integrity Protection</a> page of this document describes the options. If you're an advanced enough user to be considering a manual rEFInd installation procedure, doing the job from the Recovery HD environment may be your best option.</p>
<p>Before installing rEFInd on a Mac, you must determine whether it uses a 32-bit or 64-bit EFI implementation. Most Intel-based Macs have 64-bit EFIs, so you should use the <tt>refind_x64.efi</tt> file with them; but very early Intel-based Macs have 32-bit EFIs (and sometimes 32-bit CPUs), which require the <tt>refind_ia32.efi</tt> file. You can determine whether your Mac needs the <i>x</i>86-64 or IA32 build by typing the following command in a Mac Terminal window:</p>
<li>Open a Terminal window in which you'll type the following
commands.</li>
-<li>If you want to install rEFInd on your ESP, you must first mount it. You
- can do this by typing <b><tt>mkdir /Volumes/esp</tt></b> followed by
- <b><tt>sudo mount -t msdos /dev/disk0s1 /Volumes/esp</tt></b>. Note
- that you may need to change <tt>/dev/disk0s1</tt> to something else if
- your ESP is at an unusual location. Type <tt class="userinput">diskutil
- list</tt> or use a tool such as my <a
- href="http://www.rodsbooks.com/gdisk/">GPT fdisk (<tt>gdisk</tt>)</a>
- to examine your partition table to find your ESP if necessary.</li>
-
-<li>Type <b><tt>sudo mkdir -p /Volumes/esp/efi/refind</tt></b> to create a
+<li>If you want to install rEFInd on your ESP, you must first mount it. The
+ easy way to do this is to use the <tt>mountesp</tt> script that comes
+ with rEFInd. When you run it, the script should tell you where the ESP
+ was mounted. You can do the job manually by typing <b><tt>mkdir
+ /Volumes/ESP</tt></b> followed by <b><tt>sudo mount -t msdos
+ /dev/disk0s1 /Volumes/ESP</tt></b>. Note that you may need to change
+ <tt>/dev/disk0s1</tt> to something else if your ESP is at an unusual
+ location. Type <tt class="userinput">diskutil list</tt> or use a tool
+ such as my <a href="http://www.rodsbooks.com/gdisk/">GPT fdisk
+ (<tt>gdisk</tt>)</a> to examine your partition table to find your ESP
+ if necessary.</li>
+
+<li>Type <b><tt>sudo mkdir -p /Volumes/ESP/efi/refind</tt></b> to create a
suitable directory for rEFInd. If you want to place rEFInd on the OS X
root partition, you should adjust the pathname appropriately, as in
<tt>/efi/refind</tt>. Alternatively, you can use the Finder to create
<li>Copy the files in the <tt>refind</tt> subdirectory of the rEFInd binary
package to the like-named directory you've just created. You can do
this in the Finder or by typing <b><tt>sudo cp -r refind/*
- /Volumes/esp/efi/refind/</tt></b> in your Terminal window after
+ /Volumes/ESP/efi/refind/</tt></b> in your Terminal window after
changing into the rEFInd package's main directory.</li>
<li>Remove the file for the version of rEFInd you're not using, as in
<b><tt>sudo rm Volumes/esp/efi/refind/refind_ia32.efi</tt></b> on a Mac
with a 64-bit EFI or <b><tt>sudo rm
- /Volumes/esp/efi/refind/refind_x64.efi</tt></b> on a Mac with a 32-bit
+ /Volumes/ESP/efi/refind/refind_x64.efi</tt></b> on a Mac with a 32-bit
EFI.</li>
<li>Optionally, remove the drivers directory for the architecture you're
- not using—<tt>/Volumes/esp/efi/refind/drivers_ia32</tt> or
- <tt>/Volumes/esp/efi/refind/drivers_x64</tt>, as appropriate. You may
+ not using—<tt>/Volumes/ESP/efi/refind/drivers_ia32</tt> or
+ <tt>/Volumes/ESP/efi/refind/drivers_x64</tt>, as appropriate. You may
also want to remove some or all of the drivers for the architecture you
are using; if you don't need them, they'll slow down the start process.
See the <a href="drivers.html">page on drivers</a> for more on this
HFS+ driver provided with rEFInd is useless on Macs.</li>
<li>If this is your first installation, type <b><tt>sudo mv
- /Volumes/esp/efi/refind/refind.conf-sample
- /Volumes/esp/efi/refind/refind.conf</tt></b> (adjusting the path as
+ /Volumes/ESP/efi/refind/refind.conf-sample
+ /Volumes/ESP/efi/refind/refind.conf</tt></b> (adjusting the path as
necessary) to rename the sample configuration file so that it will
serve as a real configuration file. (Again, you can do this with the
Finder, if you prefer.)</li>
<li>"Bless" rEFInd by typing one of the following two commands:
<ul>
<li>If you're installing rEFInd on the ESP, type <tt
- class="userinput">sudo bless --mount /Volumes/esp --setBoot --file
- /Volumes/esp/efi/refind/refind_x64.efi --shortform</tt>, adjusting
+ class="userinput">sudo bless --mount /Volumes/ESP --setBoot --file
+ /Volumes/ESP/efi/refind/refind_x64.efi --shortform</tt>, adjusting
the mount point and exact path to the file as appropriate for your
installation.</li>
<li>If you're installing rEFInd to an ordinary HFS+ volume, type <tt
necessary if you're placing rEFInd somewhere else or using the
32-bit version.)</li>
</ul>
- As per the Warning earlier, <i>do not</i> use <tt>bless</tt>'s
- <tt>--info</tt> option to try to confirm the change to the boot status
- unless you're certain you do <i>not</i> have an Advanced Format hard
- disk.</li>
+ This is the step that's likely to fail if your system is booted
+ with SIP active.</li>
<li>If you don't want to reboot immediately after installing rEFInd, you
may optionally unmount the ESP by typing <tt class="userinput">sudo
umount /dev/disk0s1</tt> or <tt class="userinput">sudo umount
- /Volumes/esp</tt>. This step isn't strictly required, but if you want
+ /Volumes/ESP</tt>. This step isn't strictly required, but if you want
to keep the ESP out of your directory tree, it can be useful.</li>
</ol>
<h3>Using the <tt>--shortform</tt> Option</h3>
</a>
-<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>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. A 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>
<li>If necessary, mount the ESP or rEFInd-specific HFS+ volume, as
described in <a href="#osx">Installing rEFInd Manually Using Mac OS
- X.</a></li>
+ X.</a> (The <tt>mountesp</tt> script that comes with rEFInd will handle
+ this task.)</li>
<li>Verify that rEFInd is installed in the directory noted in step #1. If a
<tt>refind.conf</tt> file is present, rEFInd is almost certainly
<tt>bootx64.efi</tt>, <tt>boot.efi</tt>, or conceivably something else.
You may need to use <tt>sudo rm</tt> at the command line to accomplish
this task, as in <tt class="userinput">sudo rm -r
- /Volumes/esp/EFI/refind</tt>.</li>
+ /Volumes/ESP/EFI/refind</tt>.</li>
</ol>
BootOrder: 0007
Boot0007* CD/DVD Drive</pre>
-<p class="sidebar"><b>Warning:</b> As noted earlier, <tt>efibootmgr</tt> has been linked to firmware corruption on some Macs, at least with pre-3.3.0 Linux kernels. Therefore, I don't recommend using <tt>efibootmgr</tt> on Macs.</p>
-
<p>This example shows use of <tt>efibootmgr</tt>'s <tt>--verbose</tt> (<tt>-v</tt>) option to display boot programs so as to identify which one is rEFInd, followed by <tt>--delete-bootnum</tt> (<tt>-B</tt>) to delete a boot program and <tt>--bootnum</tt> (<tt>-b</tt>) to identify which one to delete. Of course, in this example there's not much else left, so you'd presumably want to install another boot program at this point! If you already have another one installed, you may want to check the <tt>BootOrder</tt> line to determine which one will take precedence when you reboot. If you don't like what it shows, you can adjust it with the <tt>--bootorder</tt> (<tt>-o</tt>) option; consult <tt>efibootmgr</tt>'s <tt>man</tt> page for details.</p>
<p>If you're not using Linux, you may be able to find a utility that serves
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/19/2012; last Web page update:
-9/19/2015, referencing rEFInd 0.9.2</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<p class="subhead">by Roderick W. Smith, <a
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
-<p>Last Web page update: 9/19/2015</p>
+<p>Last Web page update: 11/8/2015</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<ul>
+<li><b>0.10.0 (11/8/2015)</b>—I've given this version an extra-large version number bump because of some highly user-visible changes, especially for Mac users. Changes include:
+
+ <ul>
+
+ <li>I've swapped out the old icons for new ones. I've replaced the old
+ icons because the OS icons were becoming a hopeless mish-mash of
+ styles and because I wanted to consolidate the icon collection to use
+ a more limited set of original sources for record-keeping purposes.
+ If you prefer the old icons, you can continue to use them. After
+ upgrading, rename <tt>icons-backup</tt> to something else (say,
+ <tt>icons-classic</tt>) and add a line to <tt>refind.conf</tt> to
+ reference the new directory, as in <tt>icons_dir
+ icons-classic</tt>.</li>
+
+ <li>A new feature, <tt>spoof_osx_version</tt>, causes rEFInd to tell a
+ Mac that it's about to launch OS X. This alters how some Macs
+ initialize hardware, which can make secondary video chipsets work on
+ some Macs. See the comments in <tt>refind.conf-sample</tt> or on the
+ <a href="using.html">Using rEFInd</a> page for details. This feature
+ has no effect on UEFI-based PCs.</li>
+
+ <li>Another new feature enables you to adjust a Mac's System Integrity
+ Protection (SIP) settings from within rEFInd. To use this feature,
+ you must adjust two lines in <tt>refind.conf</tt>: The new
+ <tt>csr_values</tt> line sets hexadecimal values through which you
+ can rotate using a new second-row tag that's activated by the new
+ <tt>scanfor</tt> line option of <tt>csr_rotate</tt>. Thus, you must
+ add or change both the <tt>scanfor</tt> and <tt>csr_values</tt>
+ lines. See the new <a href="sip.html">rEFInd and System Integrity
+ Protection</a> page for information on how to use this new feature.
+ Although this feature can work on UEFI-based PCs if they contain the
+ necessary NVRAM variable, such systems are unlikely to have this
+ variable, and it's unlikely to be useful even if it's present.</li>
+
+ <li>If the SIP NVRAM variable is set, rEFInd now displays its current
+ value in the About screen.</li>
+
+ <li>I've renamed several support scripts: <tt>install.sh</tt> to
+ <tt>refind-install</tt>, <tt>mvrefind.sh</tt> to <tt>mvrefind</tt>,
+ and <tt>mkrlconf.sh</tt> to <tt>mkrlconf</tt>. I've also added man
+ pages for <tt>mvrefind</tt> and <tt>mkrlconf</tt>.</li>
+
+ <li>Under OS X, <tt>refind-install</tt> now checks the machine's SIP
+ status and warns the user if it's active. To help with such
+ installations, the script can also now be run from a boot of the
+ Recovery HD.</li>
+
+ <li>Under Linux, <tt>refind-install</tt> and <tt>mkrlconf</tt> now use
+ <tt>/proc/cmdline</tt> as a source for the default boot options for
+ Linux kernels, rather than trying to extract them from GRUB
+ configuration files—<i>except</i> when the <tt>--root</tt>
+ option is used, in which case the script continues to use the GRUB
+ configuration files as a source of boot options. This change should
+ help rEFInd pick up exotic boot options that GRUB computes at boot
+ time, such as Btrfs subvolume options.</li>
+
+ <li>I've added a new script, called <tt>mountesp</tt>, which mounts the
+ ESP on Macs, using the same algorithm used by
+ <tt>refind-install</tt>. This should help Mac users who want to edit
+ their rEFInd configurations.</li>
+
+ <li>I've changed the default <tt>also_scan_dirs</tt> setting from
+ <tt>boot</tt> to <tt>boot,@/boot</tt>. This change helps rEFInd pick
+ up kernels from Btrfs volumes.</li>
+
+ <li>I've changed from <tt>.zip</tt> to a tarball (<tt>.tar.gz</tt>) as
+ the file format for the source code package. This change simply
+ reflects the fact that Linux is the only supported build environment
+ for rEFInd, and tarballs are more in line with that platform than are
+ <tt>.zip</tt> files. The primary binary file format remains a
+ <tt>.zip</tt> file, with Debian packages and RPMs also
+ available.</li>
+
+ <li>My 32-bit Mac Mini suffered from a bug that caused rEFInd's
+ icon-resizing code to hang in a conversion from floating-point to
+ integer values. I've therefore adjusted the icon-resizing code to
+ avoid doing floating-point computations. This change has a drawback,
+ though: It causes some images to acquire artifacts when resized,
+ particularly on 32-bit systems. If you run into such a problem, you
+ should scale your icon(s) or banner/background image so that it does
+ not need to be resized. Sorry, but between a system crash and minor
+ graphics artifacts, the graphics artifacts are the lesser of two
+ evils.</li>
+
+ </ul></li>
+
<li><b>0.9.2 (9/19/2015)</b>—Soon after releasing 0.9.1, I started receiving bug reports about problems with it and Shim 0.8. (See <a href="https://sourceforge.net/p/refind/discussion/general/thread/2c248b11/?limit=25#1324">this thread</a> for one such report.) It turns out that the problem was not a new bug in rEFInd, but rather a change from Shim 0.7 to Shim 0.8 that made it next to useless with rEFInd. Specifically, Shim 0.8 now de-registers itself from the EFI after a follow-on program launches another one. This is done to avoid problems in a boot path in which Shim launches <tt>fallback.efi</tt>, which in turn launches <i>another</i> Shim. This creates a new problem, though: rEFInd can validate just one binary before it's "cut off" from Shim. Since rEFInd's drivers are binaries, if you use a single driver, that means that you won't be able to launch anything that requires validation via Shim. I quickly discovered a workaround, which I've implemented in this release. I consider this a "band-aid" patch, though, because it relies on a quirk of Shim's logic to bypass its de-registration. As such, the workaround in this release may break with a future Shim. A true fix will take longer to develop. I want to release this workaround version to head off further problems in the near term, though. This version also introduces a new feature, which is also Shim-related: Since version 0.7, Shim has supported launching binaries other than <tt>grubx64.efi</tt> by passing them on the command line. (Actually, Shim 0.4 supported this, but it required a broken path specification.) I've added support for this feature to <tt>install.sh</tt>: Adding the <tt>--keepname</tt> option to install.sh causes the script to preserve rEFInd's regular filename and to register the approprirate follow-on parameters to have Shim launch rEFInd by that name. This works, but is likely to be more delicate than using the default Shim follow-on name of <tt>grubx64.efi</tt>. The advantage, of course, is that rEFInd needn't "lie" about its name, which makes for less confusion in filenames. For the moment, the RPM and Debian packages I build do <i>not</i> use this new naming feature, since I can't be sure what version of Shim might be picked up. These changes do not affect users who do not use Secure Boot.</li>
<li><b>0.9.1 (9/13/2015)</b>—This version has improved the Discoverable Partitions Specification (DPS) support in a number of ways that should make it more reliable when <tt>/etc/fstab</tt> omits references to the root (<tt>/</tt>) partition or when the GPT read-only or do-not-automount options are used to control these features. A stray DPS-related debugging print command has also been removed. I've improved rEFInd's ability to guess the Linux distribution by having it examine <tt>/etc/lsb-release</tt> as well as <tt>/etc/os_release</tt>, and I've added an icon for Elementary OS. Finally, I've made improvements to rEFInd's handling of case-insensitive string comparisons, which were buggy on some EFIs, particularly when rEFInd was compiled with GNU-EFI. rEFInd is still at the mercy of the EFI and support libraries, but many problem cases should now be resolved.</li>
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 11/13/2012; last Web page update:
-9/19/2015, referencing rEFInd 0.9.2</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
</div>
+<p class="sidebar"><b>Note:</b> Macs don't (yet?) support Secure Boot, but
+as of version 10.11 ("El Capitan"), OS X uses its own new security feature,
+<i>System Integrity Protection (SIP),</i> which creates its own set of
+hoops through which rEFInd users must jump. See the <a
+href="sip.html">rEFInd and System Integrity Protection</a> page for
+details.</p>
+
<p>If you're using a computer that supports Secure Boot, you may run into extra complications. This feature is intended to make it difficult for malware to insert itself early into the computer's boot process. Unfortunately, it also complicates multi-boot configurations such as those that rEFInd is intended to manage. This page describes some <a href="#basic">Secure Boot basics</a> and two specific ways of using rEFInd with Secure Boot: <a href="#shim">Using the Shim program</a> and <a href="#preloader">using the PreLoader program.</a> (My separate <a href="http://www.rodsbooks.com/efi-bootloaders/secureboot.html">EFI Boot Loaders for Linux page on Secure Boot</a> covers the additional topics of disabling Secure Boot and adding keys to the firmware's own set of keys.) This page concludes with a look at <a href="#caveats">known bugs and limitations</a> in rEFInd's Secure Boot features.</p>
<a name="basic">
<p class="subhead">by Roderick W. Smith, <a
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
-<p>Originally written: 10/31/2015, referencing rEFInd 0.9.3</p>
+<p>Originally written: 11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<h2>What Is SIP?</h2>
</a>
-<p>To understand SIP, you should first know that Unix-like systems, including OS X, have traditionally provided a model of security in which ordinary users can read and write their own files (word processor documents, their own digital photos, etc.), but cannot write to system files (programs, system configuration files, etc.)—and users cannot even read some system files. This system security model has worked well for decades on traditional Unix systems, which have been administered by computer professionals and used by individuals with less experience. For administrative tasks, the <tt>root</tt> account is used. On Macs, this access is generally granted by the <tt>sudo</tt> command or by various GUI tools. Most Macs are single-user computers that are administered by their users. Such people often lack the knowledge of the professional system administrators who have traditionally managed Unix systems; but they must still perform system administration tasks such as installing new software and configuring network settings. OS X has always provided some measure of security by requiring users to enter their passwords before performing these dangerous tasks, and by providing GUI tools to help guide users through these tasks in a way that minimizes the risk of damage.</p>
+<p>To understand SIP, you should first know that Unix-like systems, including OS X, have traditionally provided a model of security in which ordinary users can read and write their own files (word processor documents, their own digital photos, etc.), but cannot write to system files (programs, system configuration files, etc.)—and users cannot even read some system files. This system security model has worked well for decades on traditional Unix systems, which have been administered by computer professionals and used by individuals with less experience. For administrative tasks, the <tt>root</tt> account is used. On Macs, this access is generally granted by the <tt>sudo</tt> command or by various GUI tools. Most Macs, in contrast to traditional Unix mainframes and minicomputers from the 20th century, are single-user computers that are administered by their users. Such people often lack the knowledge of the professional system administrators who have traditionally managed Unix systems; but they must still perform system administration tasks such as installing new software and configuring network settings. OS X has always provided some measure of security by requiring users to enter their passwords before performing these dangerous tasks, and by providing GUI tools to help guide users through these tasks in a way that minimizes the risk of damage.</p>
-<p>Apple has apparently decided that these safeguards are no longer sufficient. I won't try to speak for Apple or explain their motivations, but the result of Apple's decisions is SIP. With SIP active, as is the default, OS X limits your ability to perform some of these administrative tasks. You can still install and remove most third-party programs, configure your network, and so on; but some critical directories can no longer be written, even as <tt>root</tt>, and some utilities cannot be used in certain ways, even as <tt>root</tt>. These restrictions impact rEFInd because one of the affected tools, a command called <tt>bless</tt>, is required to tell the Mac to boot rEFInd rather than to boot OS X directly.</p>
+<p>Apple has apparently decided that these safeguards are no longer sufficient, at least for certain tasks, such as writing files to certain system directories and installing boot loaders. I won't try to speak for Apple or explain their motivations, but the result of Apple's decisions is SIP. With SIP active, as is the default, OS X 10.11 limits your ability to perform some of these administrative tasks. You can still install and remove most third-party programs, configure your network, and so on; but some critical directories can no longer be written, even as <tt>root</tt>, and some utilities cannot be used in certain ways, even as <tt>root</tt>. These restrictions impact rEFInd because one of the affected tools, a command called <tt>bless</tt>, is required to tell the Mac to boot rEFInd rather than to boot OS X directly.</p>
<a name="sip_enabled">
<h2>Installing rEFInd with SIP Enabled</h2>
</ol>
-<p>At this point, rEFInd should come up and enable you to boot into OS X and any other OS(es) that are already installed. You should not need to perform these steps again unless OS X re-installs its own boot loader or a subsequent OS installation overrides the default boot option. You can install an updated rEFInd and it should install correctly, provided you're installing it to the EFI System Partition (ESP). The <tt>refind-install</tt> script may complain about a failure, but because you're overwriting one rEFInd binary with another one, it should continue to boot.</p>
+<p>At this point, rEFInd should come up and enable you to boot into OS X and any other OS(es) that are already installed. You should not need to perform these steps again unless OS X re-installs its own boot loader or a subsequent OS installation overrides the default boot option. You can install an updated rEFInd and it should install correctly, provided you're installing it to the EFI System Partition (ESP). The <tt>refind-install</tt> script may complain about a failure, but because you're overwriting one rEFInd binary with another one, it should continue to boot. (If you installed rEFInd to an HFS+ partition, though, replacing the original file will require using <tt>bless</tt> to tell the firmware about the change, so updating such an installation probably won't work with SIP active.)</p>
<a name="disable">
<h3>Disabling SIP</h3>
<h4>Disabling SIP with Recovery HD</h4>
</a>
-<p>You can use the Recovery HD, as in the previous procedure, to disable SIP. To do so, boot it and launch a Terminal window, as described in the previous section. Instead of locating and running the <tt>refind-instal</tt> script, though, you should type:</p>
+<p>You can use the Recovery HD, as in the previous procedure, to disable SIP. To do so, boot it and launch a Terminal window, as described in the previous section. Instead of locating and running the <tt>refind-install</tt> script, though, you should type:</p>
<pre class="listing"># <tt class="userinput">csrutil disable</tt></pre>
<p>This command will disable SIP for all OSes that honor this setting. (In theory, multiple versions of OS X might be installed on a single computer, and all of them that support SIP should honor the SIP settings. To the best of my knowledge, no non-Apple OS honors SIP settings, although that could change.)</p>
-<p>Once you've typed this command, you can reboot the computer. When you return to your regular OS X installation, SIP should be disabled and rEFInd should install normally, as described on the <a href="installing.html">Installing rEFInd</a> page. You will also be able to use disk partitioning tools like my <a href="http://www.rodsbooks.com/gdisk/">GPT fdisk,</a> write to directories that are normally off-limits, and so on. Note that disabling SIP does <i>not</i> disable normal Unix-style protections—you'll still need to use <tt>sudo</tt> (or enter your password in a GUI dialog box) to acquire <tt>root</tt> privileges to perform these system-administration tasks. You'll be no less safe with SIP disabled under OS X 10.11 than you would be with OS X 10.10 or earlier.</p>
+<p>Once you've typed this command, you can reboot the computer. When you return to your regular OS X installation, SIP should be disabled and rEFInd should install normally, as described on the <a href="installing.html">Installing rEFInd</a> page. You will also be able to use disk partitioning tools like my <a href="http://www.rodsbooks.com/gdisk/">GPT fdisk,</a> write to directories that are normally off-limits, and so on. Note that disabling SIP does <i>not</i> disable normal Unix-style protections—you'll still need to use <tt>sudo</tt> (or enter your password in a GUI dialog box) to acquire <tt>root</tt> privileges to perform these system-administration tasks. You'll be no less safe with SIP disabled under OS X 10.11 than you would be with OS X 10.10 or earlier; you simply won't have its added protections against user error or malicious software.</p>
<p>If you want to re-enable SIP, you can do so in exactly the way you disabled it, except that you should type <tt class="userinput">csrutil enable</tt> rather than <tt class="userinput">csrutil disable</tt> in the Recovery environment.</p>
<h4>Disabling SIP with rEFInd</h4>
</a>
-<p>As described later on this page, rEFInd provides SIP control features, but they're disabled by default—except on the USB flash drive and CD-R images available from the <a href="http://www.rodsbooks.com/refind/getting.html">rEFInd downloads page.</a> On these images, the SIP control features are enabled, and can toggle between the two main modes you can set via <tt class="userinput">csrutil enable</tt> and <tt class="userinput">csrutil disable</tt> in the Recovery HD system. Thus, to disable SIP to install rEFInd, you can:</p>
+<p>As described later on this page, rEFInd
0.10.0 provides SIP control features, but they're disabled by default—except on the USB flash drive and CD-R images available from the <a href="http://www.rodsbooks.com/refind/getting.html">rEFInd downloads page.</a> On these images, the SIP control features are enabled, and can toggle between the two main modes you can set via <tt class="userinput">csrutil enable</tt> and <tt class="userinput">csrutil disable</tt> in the Recovery HD system. Thus, to disable SIP to install rEFInd, you can:</p>
<ol>
<li>Select your external boot medium to boot to rEFInd.</li>
-<li>Use the SIP "shield" icon on the second row to toggle between SIP setting, as described in more detail in <a href="#refind_manage">Using rEFInd to Manage SIP.</a></li>
+<li>Use the SIP "shield" icon on the second row to toggle between SIP setting
s, as described in more detail in <a href="#refind_manage">Using rEFInd to Manage SIP.</a></li>
</ol>
-<p>Once you install rEFInd, you can leave SIP enabled, adjust its SIP settings to enable the features from rEFInd and disable it from within your regular rEFInd, or boot again from your external rEFInd to disable SIP.</p>
+<p>Once you install rEFInd, you can leave SIP enabled, enable your newly-installed rEFInd's SIP features and use them to disable SIP, or boot again from your external rEFInd to disable SIP.</p>
<p>This procedure has the advantage of being a bit quicker than using the Recovery HD—at least, if you've already got rEFInd 0.10.0 or later on an external medium. It will also work if your Recovery HD installation is missing or broken. On the other hand, it's probably easier to boot to the Recovery HD once or twice than to download and prepare a rEFInd boot medium. Also, some Macs are a little flaky when it comes to booting from external media, so you may have trouble booting in this way. Finally, if you don't already have rEFInd on an external medium and if you don't have an optical drive, writing a USB flash drive with <tt>dd</tt> carries a small risk of accidentally trashing your hard disk, particularly if you're unfamiliar with disk devices and <tt>dd</tt>.</p>
</ul>
-<p>I've tested this method of installing rEFInd on my MacBook Air, but I can't promise it will work on all Macs—or even on an identical Mac with a configuration that's different from mine. My preference is to install rEFInd under OS X on Macs, because Apple likes to do things differently from everybody else, and so a Mac's firmware might not react in the usual way to tools like <tt>efibootmgr</tt> in Linux or <tt>bcdedit</tt> in Windows.</p>
+<p>I've tested this method of installing rEFInd on my MacBook Air (purchased in late 2014) and on my first-generation 32-bit Mac Mini, but I can't promise it will work on all Macs—or even on a Mac that's identical to one of mine but with a configuration that's different from mine. My preference is to install rEFInd under OS X on Macs, because Apple likes to do things differently from everybody else, and so a Mac's firmware might not react in the usual way to tools like <tt>efibootmgr</tt> in Linux or <tt>bcdedit</tt> in Windows.</p>
<a name="refind_manage">
<h2>Using rEFInd to Manage SIP</h2>
<li><tt class="userinput">showtools</tt>—This line specifies tools that appear on the second row of icons in rEFInd. The new tool for managing SIP is called <tt>csr_rotate</tt>, so you must uncomment <tt>showtools</tt> and add this option, or create a new <tt>showtools</tt> line.</li>
-<li><tt class="userinput">csr_values</tt>—This line lists the hexadecimal values through which you can rotate once <tt>csr_rotate</tt> is active on the <tt>showtools</tt> line. The trick to this token is selecting appropriate options. Several sites, such as <a href="http://www.idelta.info/archives/sip-rootless-internal-in-el-capitan/">this one</a> and <a href="http://osxarena.com/2015/10/guide-details-apples-system-integrity-protection-sip-for-hackintosh/">this one,</a> describe the meanings of the various options, but often not in much detail. Apple's own <tt>csrutil</tt> command sets values of 77 (disabled) or 10 (enabled). Note also that you specify hexadecimal values on this line, but without a leading <tt>0x</tt> or other hexadecimal-notation indicator. If you put gibberish values, or hexadecimal values higher than those used by SIP, rEFInd ignores the bad entries. Thus, if some of your values are being ignored, you should check your <tt>csr_values</tt> line for typos.</li>
+<li><tt class="userinput">csr_values</tt>—This line lists the hexadecimal values through which you can rotate once <tt>csr_rotate</tt> is active on the <tt>showtools</tt> line. The trick to this token is selecting appropriate options. Several sites, such as <a href="http://www.idelta.info/archives/sip-rootless-internal-in-el-capitan/">this one</a> and <a href="http://osxarena.com/2015/10/guide-details-apples-system-integrity-protection-sip-for-hackintosh/">this one,</a> describe the meanings of the various options, but often not in much detail. Apple's own <tt>csrutil</tt> command sets values of 77 (disabled) or 10 (enabled). Note also that you specify hexadecimal values on this line, but without a leading <tt>0x</tt> or other hexadecimal-notation indicator. If you specify gibberish values, or hexadecimal values higher than those used by SIP, rEFInd ignores the bad entries. Thus, if some of your values are being ignored, you should check your <tt>csr_values</tt> line for typos.</li>
</ul>
<p>Note that <i><b>both</b></i> of these options must be set appropriately. If either of them is missing or misconfigured, rEFInd will not display the new SIP tool. A typical configuration using these features might look like this:</p>
-<pre class="listing">showtools shell,memtest,gdisk,csr_rotate,apple_recovery,windows_recovery,mok_tool,about,shutdown,reboot,firmware
+<pre class="listing">showtools shell,memtest,gdisk,csr_rotate,apple_recovery,windows_recovery,about,shutdown,reboot
csr_values 10,77</pre>
<img src="func_csr_rotate.png" align="right" width="48" height="48"
alt="The SIP rotation tool rotates through all the CSR values you set"
border=2 background="gray"/>
-<p>Once these options are set and you reboot into rEFInd, you should see a new shield icon, as shown at the right. When you select this tool, rEFInd identifies the next available CSR value from the list you specified and switches to that mode, rotating back to the start of the list once the end is reached. To confirm that the SIP mode has changed, rEFInd displays, for three seconds, a message identifying the new mode.</p>
+<p>Once these options are set and you reboot into rEFInd, you should see a new shield icon on the second row, as shown at the right. When you select this tool, rEFInd identifies the next available CSR value from the list you specified and switches to that mode, rotating back to the start of the list once the end is reached. To confirm that the SIP mode has changed, rEFInd displays, for three seconds, a message identifying the new mode.</p>
<p>Whether or not you've enabled these SIP features in <tt>refind.conf</tt>, rEFInd displays the current SIP status on its "About" page:</p>
height="559" alt="rEFInd presents a graphical menu for selecting your
boot OS." border=2> </center><br />
-<p>Note the line that reads "System Integrity Protection is disabled (0x77)." This line will be updated whenever you use the CSR rotation tool, so if you've specified a large number of values and have forgotten where you are in your rotation, you can use the About screen to figure it out.</p>
+<p>Note the line that reads "System Integrity Protection is disabled (0x77)" (highlighted in this screen shot). This line will be updated whenever you use the CSR rotation tool, so if you've specified a large number of values and have forgotten where you are in your rotation, you can use the About screen to figure it out.</p>
<p>Both the summary on the About page and the CSR rotation tool depend on the presence of the <tt>csr-active-config</tt> NVRAM variable, which is where this information is stored. Thus, these features will not be present on older Macs that have not seen the presence of an OS X version that sets this variable. Likewise, you probably won't see the SIP summary in About or be able to set these values via <tt>csr_rotate</tt> and <tt>csr_values</tt> on a UEFI-based PC. (You could always create the variable on such a system in some other way, in which case rEFInd would let you adjust it, but it would have no effect on any OS except OS X.)</p>
-<p>I provide these features in rEFInd as a convenience for developers and other advanced users who have a legitimate need to adjust their SIP settings. Using rEFInd for this purpose is much faster than booting into the OS X Recovery system to make these adjustments. I discourage others from playing with these settings, since changing them inappropriately could cause problems; that's why they're not enabled by default.</p>
+<p>I provide these features in rEFInd as a convenience for developers and other advanced users who have a need to adjust their SIP settings. Using rEFInd for this purpose is much faster than booting into the OS X Recovery system to make these adjustments. I discourage others from playing with these settings, since changing them inappropriately could cause problems; that's why they're not enabled by default.</p>
<a name="conclusion">
<h2>Conclusion</h2>
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 4/19/2012; last Web page update:
-11/1/2015, referencing rEFInd 0.9.3</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<p>Note that in this example, the text immediately below the icons is white, whereas the hint text at the bottom of the screen is black. The text color is determined by the brightness of the background; rEFInd uses black text against light backgrounds and light text against dark backgrounds. This adjustment is done on a line-by-line basis, so it copes better with horizontal lines than with vertical lines.</p>
-<p>If you want to use a full-screen background but also include the rEFInd logo, you can merge the two in a graphics editor by including the <tt>refind_banner-alpha.png</tt> image from the <tt>banners</tt> subdirectory of the rEFInd package in your background.</p>
+<p>If you want to use a full-screen background but also include the rEFInd logo, you can merge the two in a graphics editor by including the <tt>refind_banner-alpha.png</tt> or <tt>refind-banner.svg</tt> image from the <tt>banners</tt> subdirectory of the rEFInd package in your background.</p>
<p>Beginning with rEFInd 0.7.8, it's possible to stretch or shrink any image to fill the screen. To do so, you should use the <tt>banner_scale</tt> option in <tt>refind.conf</tt>: Set it to <tt>noscale</tt> (the default) to use small banners as such or to crop larger images; or set it to <tt>fillscreen</tt> to adjust your banner's size to exactly fill the screen. This should be particularly handy for theme developers who want to use a full-screen background image, since you can now do this with just one image file.</p>
<h2>Icons</h2>
</a>
-<p class="sidebar">Prior to version 0.9.3, rEFInd's icons came from a variety of sources—mostly from the <a href="http://deviantdark.deviantart.com/art/Oxygen-Refit-70199755">Oxygen Refit</a> package, with OS icons from rEFIt and assorted other sources. If you prefer these icons to the new ones, you can pull them out of a rEFInd 0.9.2 package</p>
+<p class="sidebar">Prior to version 0.10.0, rEFInd's icons came from a variety of sources—mostly from the <a href="http://deviantdark.deviantart.com/art/Oxygen-Refit-70199755">Oxygen Refit</a> package, with OS icons from rEFIt and assorted other sources. If you prefer these icons to the new ones, you can pull them out of a rEFInd 0.9.2 (or earlier) package</p>
-<p>The core icons in rEFInd 0.
9.3 and later come from the <a
+<p>The core icons in rEFInd 0.
10.0 and later come from the <a
href="http://alecive.deviantart.com/art/AwOken-163570862">AwOken 2.5 icon
set,</a> with additional icons created by me, and a few others taken from
other sources. (The details are documented in the <tt>README</tt> file in
</ul>
-<p>As an example of what the combination of icons and backgrounds can do, consider my own Snowy theme, showing the same boot options as the preceding image:</p>
+<p>As an example of what the combination of icons and backgrounds can do, consider my own <a href="https://sourceforge.net/projects/refind/files/themes/">Snowy theme,</a> showing the same boot options as the preceding image:</p>
<br /><center><img src="refind-background-snowy.png" align="center"
width="750" height="563" alt="The Snowy theme uses predominantly white
<ul>
-<li><a href="https://sourceforge.net/projects/refind/files/">Snowy</a> is my own theme. It's built from (mostly) white variants of rEFInd's standard icons and includes a photo of a snowy field as a background image. It's shown earlier on this page.</li>
+<li><a href="https://sourceforge.net/projects/refind/files/themes/">Snowy</a> is my own theme. It's built from (mostly) white variants of rEFInd's standard icons and includes a photo of a snowy field as a background image. It's shown earlier on this page.</li>
<li><a href="http://ecto-plazm.deviantart.com/art/rEFInd-Icon-Theme-296571397">ecto-plazm's theme</a> was one of the first independent themes to be created for rEFInd.</li>
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-9/13/2015, referencing rEFInd 0.9.1</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-11/1/2015, referencing rEFInd 0.9.3</p>
+11/8/2015, referencing rEFInd 0.10.0</p>
<p>This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
<h2>Adjusting Boot Options</h2>
</a>
-<p>If you press the Insert, F2, or + key, rEFInd will show a menu that may hold additional options, depending on the OS type. (OS X and Linux are most likely to hold interesting options on their submenus.) The following figure shows the submenu for Mac OS X. You can use this menu much like the main menu; move the cursor to select the option you want to use, then press the Enter key to launch the boot loader with the selected options. Press the Esc key or select <tt>Return to Main Menu</tt> to return to the main menu.</p>
+<p>If you press the Insert, F2, or + key, rEFInd will show a menu that may hold additional options, depending on the OS type. (OS X and Linux are most likely to hold interesting options on their submenus.) The following figure shows the submenu for Mac OS X. You can use this menu much like the main menu; move the cursor to select the option you want to use, then press the Enter key to launch the boot loader with the selected options. Press the Esc key or select <tt>Return to Main Menu</tt> to return to the main menu. (See the <a href="linux.html">Methods of Booting Linux</a> page for information on what you might see on a Linux submenu page.)</p>
<br /><center><img src="submenu.png" align="center" width="499"
height="228" alt="rEFInd submenus enable you to set session-specific
<p><a href="index.html">Go to the main rEFInd page</a></p>
-<p><a href="sip.html">Installing rEFInd using El Capitan</a></p>
+<p><a href="sip.html">rEFInd and System Integrity Protection</a></p>
<p><a href="http://www.rodsbooks.com/">Return</a> to my main Web page.</p>
</body>
fi
MountPoint="/Volumes/ESP"
mkdir /Volumes/ESP &> /dev/null
- mount -t msdos "$Esp" /Volumes/ESP
+ mount -t msdos "$Esp" $MountPoint
# Some systems have HFS+ "ESPs." They shouldn't, but they do. If this is
# detected, mount it as such and set appropriate options.
if [[ $? != 0 ]] ; then
- mount -t hfs "$Esp" /Volumes/Esp
+ mount -t hfs "$Esp" $MountPoint
if [[ $? != 0 ]] ; then
echo "Unable to mount ESP!\n"
exit 1
<key>ProductName</key>
<string>rEFInd</string>
<key>ProductVersion</key>
- <string>0.9.2</string>
+ <string>0.10.0</string>
</dict>
</plist>
ENDOFHERE
echo "CAUTION: This Linux installation uses a 32-bit kernel. 32-bit EFI-based"
echo "computers are VERY RARE. If you've installed a 32-bit version of Linux"
echo "on a 64-bit computer, you should manually install the 64-bit version of"
- echo "rEFInd. If you're installing on a Mac, you should do so from OS X. If"
- echo "you're positive you want to continue with this installation, answer 'Y'"
- echo "to the following question..."
+ echo "rEFInd. If you're positive you want to continue with this installation,"
+ echo "answer 'Y' to the following question..."
echo
echo -n "Are you sure you want to continue (Y/N)? "
ReadYesNo
Summary: EFI boot manager software
Name: refind
-Version: 0.9.2.7
+Version: 0.10.0
Release: 1%{?dist}
Summary: EFI boot manager software
License: GPLv3
# Copy documentation to /usr/share/doc/refind-%{version}
mkdir -p $RPM_BUILD_ROOT/usr/share/doc/refind-%{version}
-cp -a docs/* $RPM_BUILD_ROOT/usr/share/doc/refind-%{version}/
+cp -a docs/Styles $RPM_BUILD_ROOT/usr/share/doc/refind-%{version}/
+cp -a docs/refind $RPM_BUILD_ROOT/usr/share/doc/refind-%{version}/
install -Dp -m0644 NEWS.txt COPYING.txt LICENSE.txt README.txt CREDITS.txt $RPM_BUILD_ROOT/usr/share/doc/refind-%{version}
+# Copy man pages to /usr/share/man/man8
+mkdir -p $RPM_BUILD_ROOT/usr/share/man/man8
+install -Dp -m0644 docs/man/mvrefind.8 $RPM_BUILD_ROOT/usr/share/man/man8
+install -Dp -m0644 docs/man/mkrlconf.8 $RPM_BUILD_ROOT/usr/share/man/man8
+
# Copy keys to /etc/refind.d/keys
mkdir -p $RPM_BUILD_ROOT/etc/refind.d/keys
install -Dp -m0644 keys/* $RPM_BUILD_ROOT/etc/refind.d/keys
%files
%defattr(-,root,root -)
%doc /usr/share/doc/refind-%{version}
+%doc /usr/share/man/man8
/usr/sbin/mkrlconf
/usr/sbin/mvrefind
/usr/share/refind-%{version}
# thus wiping out the just-updated files.
%changelog
+* Sun Nov 8 2015 R Smith <rodsmith@rodsbooks.com> - 0.10.0
+- Updated spec file for 0.10.0
* Sat Sep 19 2015 R Smith <rodsmith@rodsbooks.com> - 0.9.2
- Updated spec file for 0.9.2
* Sun Sep 13 2015 R Smith <rodsmith@rodsbooks.com> - 0.9.1
- Updated spec file for 0.8.7
* Sun Feb 8 2015 R Smith <rodsmith@rodsbooks.com> - 0.8.6
- Updated spec file for 0.8.6
-* Sun Feb 2 2015 R Smith <rodsmith@rodsbooks.com> - 0.8.5
+* Sun Feb 1 2015 R Smith <rodsmith@rodsbooks.com> - 0.8.5
- Updated spec file for 0.8.5
* Mon Dec 8 2014 R Smith <rodsmith@rodsbooks.com> - 0.8.4
- Updated spec file for 0.8.4
if (AboutMenu.EntryCount == 0) {
AboutMenu.TitleImage = BuiltinIcon(BUILTIN_ICON_FUNC_ABOUT);
- AddMenuInfoLine(&AboutMenu, L"rEFInd Version 0.9.2.8");
+ AddMenuInfoLine(&AboutMenu, L"rEFInd Version 0.10.0");
AddMenuInfoLine(&AboutMenu, L"");
AddMenuInfoLine(&AboutMenu, L"Copyright (c) 2006-2010 Christoph Pfisterer");
AddMenuInfoLine(&AboutMenu, L"Copyright (c) 2012-2015 Roderick W. Smith");
