X-Git-Url: https://code.delx.au/refind/blobdiff_plain/f92a7032373fc63e9d8946574d4fb42464d1c916..bfe73b5fa6321273b7cf86b02a3c2d114a167bc9:/docs/refind/drivers.html diff --git a/docs/refind/drivers.html b/docs/refind/drivers.html index 0a86376..a497a71 100644 --- a/docs/refind/drivers.html +++ b/docs/refind/drivers.html @@ -17,7 +17,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com
Originally written: 4/19/2012; last Web page update: -3/1/2015, referencing rEFInd 0.8.7
+9/19/2015, referencing rEFInd 0.9.2This 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!
@@ -228,7 +228,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com 2.0 Btrfs driver. I've tested this driver with a simple one-partition filesystem and with a filesystem that spans two physical devices (although I've made no attempt to ensure that the driver can actually - read files written to both devices). Lamuel Liao has used the driver + read files written to both devices). Samuel Liao has used the driver with a compressed Btrfs volume. The driver will handle subvolumes, but you may need to add kernel options if you're booting a Linux kernel directly from a filesystem that uses subvolumes. For instance, on a @@ -260,14 +260,15 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com mainly because it compiled cleanly with no extra work, aside from providing a Makefile entry for it. + +All of these drivers rely on filesystem wrapper code written by rEFIt's author, Christoph Phisterer.
- +If you want to use one or more of these drivers, you can install them from the rEFInd binary package from the refind/drivers_arch directory, where arch is a CPU architecture code—x64 or ia32. The files are named after the filesystems they handle, such as ext4_x64.efi for the 64-bit ext4fs driver. You should copy the files for the filesystems you want to use to the drivers or drivers_arch subdirectory of the main rEFInd installation directory. (You may need to create this subdirectory.) Be careful to install drivers only for your own architecture. Attempting to load drivers for the wrong CPU type will cause a small delay at best, or may cause the computer to crash at worst. I've placed rEFInd's drivers in directories that are named to minimize this risk, but you should exercise care when copying driver files.