href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
<p>Originally written: 3/14/2012; last Web page update:
-6/21/2012, referencing rEFInd 0.4.3</p>
+6/23/2012, referencing rEFInd 0.4.4</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>
caused by a truncated DevicePath to the shell, which includes the
shell's pathname but not the device identifier.</li>
- <li>The 32-bit build of rEFInd displays corrupted volume labels for
- filesystems handled by built-in drivers, but not for the drivers
- provided with rEFInd. This is presumably related to the 32-bit
- driver bug noted below.</li>
-
<li>The code is in need of review to search for memory leaks and
similar problems.</li>
<ul>
- <li>The 32-bit versions of the drivers return filesystem labels that
- omit the first two characters of the name. If the name is shorter
- than two characters, the driver may return the wrong volume's
- label. The 64-bit builds seem to be unaffected by this bug.</li>
-
<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