X-Git-Url: https://code.delx.au/refind/blobdiff_plain/7c898f4a26b66344e4cc8ed5c2e272d5ea0a71dc..87bc9afcef9d2fc27b8bcff46fa9c88e8962fcae:/docs/refind/todo.html

diff --git a/docs/refind/todo.html b/docs/refind/todo.html
index 993af2d..d890e43 100644
--- a/docs/refind/todo.html
+++ b/docs/refind/todo.html
@@ -15,7 +15,7 @@
 href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
 <p>Originally written: 3/14/2012; last Web page update:
-8/12/2012, referencing rEFInd 0.4.5</p>
+12/16/2012, referencing rEFInd 0.6.0</p>
 
 
 <p>I'm a technical writer and consultant specializing in Linux technologies. 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>
@@ -131,6 +131,14 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
     <ul>
 
+    <li>The support for booting legacy (BIOS) OSes on UEFI-based PCs
+	currently has a number of limitations. Most importantly, it works
+	off of the list of boot devices stored in the computer's NVRAM. I'd
+	prefer to have it scan disks and partitions, as the Mac's legacy
+	boot support does. Also, the UEFI legacy boot code presents empty
+	optical drives and uses generic icons rather than OS-specific
+	icons.</li>
+
     <li>Currently, rEFInd can detect whether it's compiled for <i>x</i>86
 	or <i>x</i>86-64 systems and displays this information in its
 	"About" screen (<tt>AboutrEFInd()</tt> in <tt>main.c</tt>). I'd
@@ -157,6 +165,13 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 	from the partition data is harder than extracting the volume's
 	label or counting up the filesystem numbers.</li>
 
+    <li>Currently, if a filesystem's label comes up empty, rEFInd
+	substitutes the size, so you get displays like <tt>boot
+	EFI\foo\bar.efi from 90 GiB volume</tt>. I'd like to add more
+	checks to substitute the GPT <i>partition</i> label if the
+	<i>filesystem</i> label comes up empty, or add a filesystem type
+	identifier to the size.</li>
+
     <li>The default_selection option in refind.conf could be improved by
 	supporting a list of default options, so that if the first item
 	isn't found, rEFInd will try to boot the second one in the list,
@@ -187,13 +202,25 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
     <ul>
 
-    <li>I'd like to find a way to get rEFInd to launch BIOS boot loaders on
-	UEFI-based systems. This option currently works only on
-	Macs&mdash;or at least, I've not gotten it to work on any of my
-	UEFI-based PCs. (I've done some experiments to try to get this to
-	work, but so far without success. If you'd like to help on this, <a
-	href="mailto:rodsmith@rodsbooks.com">e-mail me</a> for my
-	thoughts.)</li>
+    <li>When in Secure Boot mode, rEFInd can launch just one driver that's
+	signed with a shim key or MOK. The second and later drivers
+	generate "access denied" errors. <!-- I think this is because of
+	the fast-and-loose sample code I borrowed from shim, which re-uses
+	rEFInd's own image handle (the <tt>image_handle</tt> variable in
+	<tt>start_image()</tt>) for launching shim/MOK-signed binaries. The
+	result is that when the second driver is loaded, it can't register
+	itself with the firmware because the firmware believes it's already
+	been registered. The solution is likely to involve creating a child
+	image handle rather than re-using rEFInd's own image handle, but
+	this is likely to be tedious to do&mdash;see
+	<tt>/usr/local/UDK2010/MyWorkSpace/MdeModulePkg/Core/Dxe/Image/Image.c</tt>
+	for the reference UEFI implementation. --> </li>
+
+    <li>When setting a resolution higher than about 800x600 (or maybe even
+	640x480) in text mode, the text displayed by rEFInd, and on some
+	systems shells and other programs launched from rEFInd, is
+	restricted to an 80x24-character area in the top-left corner of the
+	screen.</li>
 
     <li>The <a href="http://www.rodsbooks.com/gb-hybrid-efi/">Gigabyte
 	Hybrid EFI</a> has a bug that causes the allegedly case-insensitive
@@ -281,9 +308,6 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 	boot. Perhaps this could be done via a separate tool that could be
 	launched much like the shell or <tt>gptsync</tt>.</li>
 
-    <li>I'd like to give the user the ability to set custom options on a
-	single-boot basis, similar to what's possible in GRUB.</li>
-
     <li>A way to set the color of the font would be useful for theming
         purposes.</li>
 
@@ -295,20 +319,15 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 	written in a cross-platform GUI toolkit, so that a single code base
 	can be used on any of the major OSes.</li>
 
-    <li>A way to "source" one configuration file from another one would be
-	helpful for some types of configuration scripts. (This would enable
-	overriding options in a secondary file without modifying the
-	default original file, for instance.)</li>
-
     </ul></li> <!-- New features -->
 
     <li><b>Improvements to the EFI drivers:</b>
 
     <ul>
 
-    <li>Drivers for additional filesystems are required. Given the recent
-	shift to ext4fs, that should be the priority; however, other Linux
-	filesystems, UDF, and perhaps others would all be welcome
+    <li>Drivers for additional filesystems are desirable. Given the talk of
+	shifting to Btrfs, that should be the priority; however, other
+	Linux filesystems, UDF, and perhaps others would all be welcome
 	additions. Also along these lines, adding drivers for Linux LVM and
 	RAID setups would be useful, too.</li>
 
@@ -320,9 +339,6 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 	href="http://www.rodsbooks.com/bios2uefi/">DUET</a>). Nonetheless,
 	I'd like to track down the cause and fix it.</li>
 
-    <li>The driver installation procedure could be improved, perhaps by
-        adding support for drivers to the <tt>install.sh</tt> script.</li>
-
     <li>The HFS+ driver returns a volume label of "HFS+ volume", no matter
         what the volume's real label is.</li>