X-Git-Url: https://code.delx.au/refind/blobdiff_plain/85f7e52b653f9e618ad57d511ed01db94ae3b2b3..7b85c1b8c0aca2e8e9443083f628e5493bc64cfa:/docs/refind/todo.html
diff --git a/docs/refind/todo.html b/docs/refind/todo.html
index 7e7356b..92b4a38 100644
--- a/docs/refind/todo.html
+++ b/docs/refind/todo.html
@@ -15,7 +15,7 @@
href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
Originally written: 3/14/2012; last Web page update:
-5/20/2012, referencing rEFInd 0.4.0
+12/6/2012, referencing rEFInd 0.5.0
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!
@@ -131,6 +131,14 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
+ - 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.
+
- Currently, rEFInd can detect whether it's compiled for x86
or x86-64 systems and displays this information in its
"About" screen (AboutrEFInd() in main.c). I'd
@@ -175,19 +183,37 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
and/or initial RAM disks relative to the rEFInd directory (or the
boot loader's directory, in the case of initrds).
+ - Various options (dont_scan_dirs, also_scan_dirs,
+ scan_driver_dirs, etc.) refer to directories or files,
+ either on the ESP or on all partitions. A way to identify specific
+ partitions for these options would be useful in some
+ situations.
+
Known bugs that need squashing:
- - 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—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, e-mail me for my
- thoughts.)
+ - 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.
+
+ - 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.
- The Gigabyte
Hybrid EFI has a bug that causes the allegedly case-insensitive
@@ -232,7 +258,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
shell's pathname but not the device identifier.
- The code is in need of review to search for memory leaks and
- similar problems.
+ similar problems.
@@ -257,8 +283,10 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
forum thread for more information.
I'd like to find a way to enable users to enter customizations for
- boot options and then save them to the refind.conf
- file.
+ boot options and then save them to the refind.conf file.
+ One possible way to implement this would be to have manual boot
+ stanzas override auto-detected boot loader definitions for the same
+ boot loader file.
It should be possible to override specific auto-detected boot
loader settings—say, to disable one specific boot loader or
@@ -273,8 +301,11 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
boot. Perhaps this could be done via a separate tool that could be
launched much like the shell or gptsync.
- 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.
+ A way to set the color of the font would be useful for theming
+ purposes.
+
+ Going further, the ability to load arbitrary other fonts, ideally
+ in a standard format, would be desirable for theming purposes.
A GUI configuration tool would be nice, but it's low on my personal
priority list. If you'd like to contribute, I prefer something
@@ -287,21 +318,6 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
- - The drivers I've built fail to load on a 32-bit Mac Mini; I get an
- "incompatible version" error message at an EFI shell, or an error
- code of 80000019 when rEFInd tries to load them. (These two
- messages are equivalent.) I suspect the problem is related to the
- EFI version 1.x used on the Mac, as opposed to UEFI
- 2.x used on PCs. I'm looking into the problem. In the
- meantime, if you have this problem, I recommend tracking down
- equivalent drivers from other sources. (See the drivers page for some pointers.) I'd
- appreciate hearing from
- you if you have problems along these lines. Please tell me what
- type of computer you're using, and especially the firmware version
- data (from rEFInd's "about" screen). This may help me narrow down
- the cause.
-
- 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
@@ -316,12 +332,13 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
href="http://www.rodsbooks.com/bios2uefi/">DUET). Nonetheless,
I'd like to track down the cause and fix it.
- - The driver installation procedure could be improved, perhaps by
- adding support for drivers to the install.sh script.
-
- The HFS+ driver returns a volume label of "HFS+ volume", no matter
what the volume's real label is.
+ - This may not be possible, or it may require a new driver, but a way
+ to have the drivers access files (like a Linux loopback mount) is
+ desirable.
+