From 293749865fc028016e6896402afd37d7021a5e48 Mon Sep 17 00:00:00 2001 From: srs5694 Date: Wed, 5 Dec 2012 20:49:23 -0500 Subject: [PATCH] Refinements, mostly to shim/MOK support. --- NEWS.txt | 7 ++ docs/refind/configfile.html | 2 +- docs/refind/todo.html | 14 ++++ filesystems/fsw_efi.c | 2 +- install.sh | 11 +++- refind.conf-sample | 4 +- refind/config.c | 2 +- refind/lib.c | 66 +++++++++---------- refind/main.c | 102 ++++++++++++++++++------------ refind/mok.c | 123 ++++++++++++++++++++++++++++-------- refind/mok.h | 40 ++---------- 11 files changed, 232 insertions(+), 141 deletions(-) diff --git a/NEWS.txt b/NEWS.txt index 60a94c1..c8adbff 100644 --- a/NEWS.txt +++ b/NEWS.txt @@ -1,6 +1,13 @@ 0.5.0 (??/??/2012): ------------------- +- Changed refind.conf-sample to uncomment the scan_all_linux_kernels + option by default. If this option is deleted or commented out, the + program default remains to not scan all Linux kernels; but with + increasing numbers of distributions shipping with kernels that include + EFI stub loader support, setting the configuration file default to scan + for them makes sense. + - Modified the "resolution" token so that it affects text mode as well as graphics mode. On my systems, though, the actual text area is still restricted to an 80x25 area. (This seems to be a firmware limitation; my diff --git a/docs/refind/configfile.html b/docs/refind/configfile.html index ce7b893..583e601 100644 --- a/docs/refind/configfile.html +++ b/docs/refind/configfile.html @@ -221,7 +221,7 @@ timeout 20 scan_all_linux_kernels None - When set, causes rEFInd to add Linux kernels (files with names that begin with vmlinuz or bzImage) to the list of EFI boot loaders, even if they lack .efi filename extensions. The hope is that this will simplify use of rEFInd on distributions that provide kernels with EFI stub loader support but that don't give those kernels names that end in .efi. Of course, the kernels must still be stored on a filesystem that rEFInd can read, and in a directory that it scans. (Drivers and the also_scan_dirs options can help with those issues.) Note that this option can cause unwanted files to be improperly detected and given loader tags, such as older kernels without EFI stub loader support. For this reason, it's disabled by default, but that may change in the future. + When set, causes rEFInd to add Linux kernels (files with names that begin with vmlinuz or bzImage) to the list of EFI boot loaders, even if they lack .efi filename extensions. The hope is that this will simplify use of rEFInd on distributions that provide kernels with EFI stub loader support but that don't give those kernels names that end in .efi. Of course, the kernels must still be stored on a filesystem that rEFInd can read, and in a directory that it scans. (Drivers and the also_scan_dirs options can help with those issues.) Note that this option can cause unwanted files to be improperly detected and given loader tags, such as older kernels without EFI stub loader support. Versions of rEFInd prior to 0.5.0 left this option commented out in the refind.conf-sample file, but as of version 0.5.0, this option is enabled in the default configuration file. The program default remains to not scan for such kernels, though, so you can delete or uncomment this option to keep them from appearing in your boot menu. default_selection diff --git a/docs/refind/todo.html b/docs/refind/todo.html index 5919dbc..cf9de2d 100644 --- a/docs/refind/todo.html +++ b/docs/refind/todo.html @@ -195,6 +195,20 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com