href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-4/25/2013, referencing rEFInd 0.6.9</p>
+6/27/2013, referencing rEFInd 0.7.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>
systems with a limited number of configurations. Therefore, if you
try rEFInd and run into bugs, please report them to me!</li>
- <li>I have little talent with graphics manipulation programs, so
- rEFInd's boot logo, such as it is, is pretty weak. If you have
- artistic talent and would like to create a rEFInd logo, please feel
- free to send it to me. I won't make any final decision about
- changes until at least June 30 of 2012.</li>
-
<li>rEFIt's original design, and hence rEFInd's design, enables easy
theming by replacing icon files. If you'd like to design a new
theme for rEFInd, feel free to submit it. I might or might not
the list, it will take precedence over the normal hard disk
default.</li>
- <li>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.</li>
+ <li>Along the lines of the previous item, the
+ <tt>default_selection</tt> 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.</li>
<li>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
<ul>
+ <li>I've been receiving reports of blank screens when using rEFInd on
+ some recent Mac models. I've investigated this with the help of one
+ user, and I suspect that Apple has made changes to its firmware
+ that are likely to affect just about any EFI program. I don't know
+ how to fix the problem at the moment, though; I need both
+ documentation and access to an afflicted computer to do the
+ necessary work, and I have neither.</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
<tt>StriCmp()</tt> function to perform a case-sensitive comparison.
loader settings—say, to disable one specific boot loader or
change its icon.</li>
+ <li>The ability to rotate the display for users who rotate their
+ monitors would be helpful.</li>
+
<li>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
<ul>
- <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>
-
- <li>As detailed on the <a href="drivers.html">drivers page,</a> there
- are performance issues with the drivers on some systems. I suspect
- that most "real" computers aren't greatly affected (in my tests,
- the problem is worst with VirtualBox, and the next worst is a
- system that uses <a
- href="http://www.rodsbooks.com/bios2uefi/">DUET</a>). Nonetheless,
- I'd like to track down the cause and fix it.</li>
+ <li>Drivers for additional filesystems are desirable. Only XFS and JFS
+ are missing from the major Linux filesystems. UDF would also be a
+ welcome addition, as might drivers for other OSes (say, for the
+ BSDs, especially if BSD developers create a boot loader similar to
+ Linux's EFI stub loader). Also along these lines, adding drivers
+ for Linux LVM and RAID setups would be useful.</li>
<li>The HFS+ driver returns a volume label of "HFS+ volume", no matter
what the volume's real label is.</li>