X-Git-Url: https://code.delx.au/refind/blobdiff_plain/349ce35386aee70fdc9d323514228e529d9c1816..107d80e5276d89f8b0763f6aa208e60d540ca06b:/NEWS.txt

diff --git a/NEWS.txt b/NEWS.txt
index d9d52da..61ae509 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -1,4 +1,33 @@
-0.8.1 (5/??/2014):
+0.8.2 (6/8/2014):
+-----------------
+
+- Changed behavior when default_selection is not set: It now boots the
+  previously-booted loader, assuming it's still available; if not, rEFInd
+  boots the first loader (as it does now). Behavior is unchanged if
+  default_selection is set. Note that this behavior depends on the ability
+  of rEFInd to store an EFI variable in NVRAM. It therefore fails on
+  systems with flaky NVRAM storage. You can view the previously-booted
+  loader in the
+  /sys/firmware/efi/efivars/PreviousBoot-36d08fa7-cf0b-42f5-8f14-68df73ed3740
+  variable under Linux.
+
+- Added icon for Mageia Linux (os_mageia.png).
+
+- Fixed bug that could misidentify a not-quite-GUID as a GUID in a
+  manual boot stanza's "volume" line.
+
+- I've updated my personal build system, and therefore the rEFInd Makefiles
+  and related files, to use TianoCore UDK2014 rather than UDK2010.
+
+- Added "deep_uefi_legacy_scan" token. When not set (the default), rEFInd
+  does not modify EFI NVRAM settings when scanning for BIOS-mode boot
+  loaders on UEFI-based (non-Mac) computers. Some computers require
+  uncommenting this setting for rEFInd to reliably detect some BIOS-mode
+  boot devices. Passing "0", "off", or "false" as an option resets it to
+  the default value (useful in a loaded secondary configuration file to
+  override a setting in the main file).
+
+0.8.1 (5/15/2014):
 ------------------
 
 - Fixed bug that could cause rEFInd to fail to detect boot loaders stored
@@ -14,7 +43,7 @@
 - Improved centering of legacy boot option descriptions on some systems'
   screens.
 
-- Fixed bug that could cause a BIOS-mode boot to launch an inappropriate
+- Fixed bug that could cause a BIOS-mode boot to boot from an inappropriate
   device if that device had an innately high boot priority (as set by the
   firmware).