-0.9.1 (?/??/2015):
+0.9.3 (??/??/2015):
+-------------------
+
+- Added detection of System Integrity Protection (SIP; aka "rootless") mode
+ to OS X portion of install.sh script. When detected, and if no existing
+ rEFInd installation is found, the script now prints a warning and brief
+ instructions of how to enter the Recovery mode to install rEFInd and
+ suggests aborting the installation. (The user can override and attempt
+ installation anyhow.) If SIP is detected along with an existing rEFInd
+ installation, the script moderates the warning and explains that an
+ update of a working rEFInd will probably succeed, but that re-installing
+ to fix a broken rEFInd will probably fail.
+
+- Added new "spoof_osx_version" token, which takes an OS X version number
+ (such as "10.9") as an option. This feature, when enabled, causes rEFInd
+ to tell a Mac's firmware that the specified version of OS X is being
+ launched. This option is usually unnecessary, but it can help properly
+ initialize some hardware -- particularly secondary video devices. OTOH,
+ on some Macs it can cause hardware (notably keyboards and mice) to become
+ unresponsive, so you should not use this option unnecessarily.
+
+- Worked around an EFI bug that affected my 32-bit Mac Mini: That system
+ seems to have a broken EFI, or possibly a buggy CPU, that causes some
+ (but not all) conversions from floating-point to integer numbers to hang
+ the computer. Such operations were performed only in rEFInd's
+ graphics-resizing code, and so would manifest only when icons or
+ background images were resized. My fix eliminates the use of
+ floating-point operations in the affected function, which eliminates the
+ crashes. There may be some degradation in the quality of resized images,
+ though, particularly on 32-bit systems. (64-bit systems use larger
+ integers, which enable greater precision in my floating-point
+ workaround.)
+
+- Under OS X, install.sh can now be run from the recovery system. This may
+ help work around OS X 10.11's problems with System Integrity Protection,
+ since it should be possible to reboot into the recovery system to install
+ rEFInd without disabling SIP for the main installation, even for just one
+ boot.
+
+0.9.2 (9/19/2015):
------------------
+- Added "--keepname" option to install.sh. This option causes install.sh
+ to keep refind_x64.efi named as such rather than rename it as grubx64.efi
+ when using Shim. This option is meaningful only if the --shim option is
+ also used. This option passes the refind_x64.efi filename as an option to
+ Shim, which overrides the default filename of grubx64.efi. A big caveat:
+ Only Shim 0.7 and later supports this feature. (Shim 0.4 also works if a
+ refind_x64.efi is referred to as "\refind_x64.efi" on the command line,
+ but the need for a leading backslash to refer to a file in the same
+ directory as Shim is so confusing and wrong that I cannot in good
+ conscience support it.) I've not seen signed Shim binaries between 0.4
+ and 0.7, so I don't know if any of them might work.
+
+- Implemented a workaround for a bug in Shim 0.8 that prevented
+ authentication of more than one binary. If any filesystem drivers were
+ installed, the first one would be verified, leaving rEFInd unable to
+ launch anything else unless it was signed by a key in the computer's main
+ Secure Boot db list.
+
+0.9.1 (9/13/2015):
+------------------
+
+- When rEFInd identifies the root (/) partition via the Freedesktop.org
+ Discoverable Partitions Specification, it now checks two of the
+ partition's attributes, as per the DPS (see
+ http://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/):
+ - The partition's read-only attribute determines whether to pass a "rw"
+ or "ro" option to the kernel.
+ - If the partition's do-not-automount flag is set, rEFInd will not pass
+ it as a "root=" option to the kernel. This flag can be used to remove
+ all but one partition from consideration as a root (/) partition if a
+ system has more than one with the correct type code.
+
- Improved Freedesktop.org Discoverable Partitions Specification support:
Previously, if no refind_linux.conf file was present but an /etc/fstab
file was found, rEFInd ignored the Discoverable Partitions Specification