X-Git-Url: https://code.delx.au/refind/blobdiff_plain/775c835c500538b43f65469afadc2af7b61cf65b..87bc9afcef9d2fc27b8bcff46fa9c88e8962fcae:/docs/refind/todo.html
diff --git a/docs/refind/todo.html b/docs/refind/todo.html
index 9201b69..d890e43 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/16/2012, referencing rEFInd 0.6.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
@@ -157,23 +165,62 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
from the partition data is harder than extracting the volume's
label or counting up the filesystem numbers.
+ - Currently, if a filesystem's label comes up empty, rEFInd
+ substitutes the size, so you get displays like boot
+ EFI\foo\bar.efi from 90 GiB volume. I'd like to add more
+ checks to substitute the GPT partition label if the
+ filesystem label comes up empty, or add a filesystem type
+ identifier to the size.
+
+ - 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,
+ and so on. This could be handy in case a driver fails to load, or
+ to provide an override in case the user inserts a specific
+ removable disk—by placing the removable disk's name first in
+ the list, it will take precedence over the normal hard disk
+ default.
+
+ - Along the lines of the previous item, the default_selection might
+ be expanded to support some form of specification of disk types, as
+ in a special entry for any optical disk or any external disk, no
+ matter what its name is.
+
- It would be useful to be able to specify paths to boot loaders
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
@@ -193,9 +240,9 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
implementation, and a dismal one at that, so I'm inclined to just
let it go.
- - The Shutdown option works correctly on Macs, but not on UEFI-based PCs.
- On such systems, Shutdown reboots the computer. This should be
- fixed.
+ - The Shutdown option works correctly on Macs, but not on UEFI-based
+ PCs. On such systems, Shutdown reboots the computer. This should be
+ fixed.
- The media-ejection feature (F12) should be extended to work on
UEFI-based PCs and early Macs. At the moment, it relies on an
@@ -206,13 +253,19 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
ignoring new media or keeping old media that have been ejected.
This should be investigated and fixed.
- - The re-scan feature renders the user interface immobile until
- the re-scan is complete. This is usually just a second or two,
- but it can be longer if an optical disc needs to be spun up.
- Adding a temporary "scanning media" notice would be helpful.
+ - The "scanning for new boot loaders" message that appears during the
+ re-scan feature is primitive. Some sort of dynamic icon would be
+ nice, but perhaps impractical, given the single-tasking nature of
+ EFI.
+
+ - On my Mac Mini, launching a shell, returning, and performing a
+ re-scan causes the system to be unable to launch the shell again. I
+ have not observed this behavior on UEFI-based PCs. It seems to be
+ caused by a truncated DevicePath to the shell, which includes the
+ 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.
@@ -237,8 +290,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
@@ -253,8 +308,16 @@ 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
+ written in a cross-platform GUI toolkit, so that a single code base
+ can be used on any of the major OSes.
@@ -262,24 +325,9 @@ 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
+
- 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.
@@ -289,10 +337,14 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
the problem is worst with VirtualBox, and the next worst is a
system that uses DUET). Nonetheless,
- I'd like to track down the cause and fix it.
+ I'd like to track down the cause and fix it.
+
+ - The HFS+ driver returns a volume label of "HFS+ volume", no matter
+ what the volume's real label is.
- - The driver installation procedure could be improved, perhaps by
- adding support for drivers to the install.sh script.
+
- 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.