X-Git-Url: https://code.delx.au/refind/blobdiff_plain/92a37087e2c2cab21d68e0328f1408912869e6fa..b1ba9f9e7edcf78bb9bfeb5451bff0ecf1752f90:/docs/refind/drivers.html diff --git a/docs/refind/drivers.html b/docs/refind/drivers.html index 2550030..5c8ca65 100644 --- a/docs/refind/drivers.html +++ b/docs/refind/drivers.html @@ -15,10 +15,10 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com

Originally written: 4/19/2012; last Web page update: -8/25/2013, referencing rEFInd 0.7.4

+12/8/2014, referencing rEFInd 0.8.4

-

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!

+

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!

@@ -163,7 +163,7 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com

-
  • You can load a filesystem driver to gain access to files on a filesystem other than FAT (or HFS+ on Macs or ISO-9660 on some systems). This is most likely to be useful on a Linux installation, since a filesystem driver can enable you to store a Linux kernel with EFI stub loader or for use by ELILO on a Linux-native filesystem if your ESP is getting crowded.
    • +
  • You can load a filesystem driver to gain access to files on a filesystem other than FAT (or HFS+ on Macs or ISO-9660 on some systems). This is most likely to be useful on a Linux installation, since a filesystem driver can enable you to store a Linux kernel with EFI stub loader or for use by ELILO on a Linux-native filesystem if your EFI System Partition (ESP) is getting crowded.
  • You can load a driver for a plug-in disk controller to give the EFI access to its disks. Note that this is not required if you place your boot loader (and perhaps your OS kernel) on another disk, or if the plug-in disk controller includes EFI-capable firmware. It could be handy, perhaps in conjunction with a filesystem driver, to enable the EFI to read a boot loader or kernel from a disk on a plug-in controller, though.
    • @@ -207,29 +207,36 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com

    href="https://github.com/falstaff84/rEFInd">modified the rEFIt/rEFInd ext2fs driver so that it could handle ext4fs. I'm including this as a separate driver from the ext2fs driver, although the ext4fs version - can handle ext2fs and ext3fs, too. (I may eventually retire the - original ext2fs driver, but I want to be conservative about this in - case there's an undiscovered problem with the new driver.) This driver - has some limitations. Most notably, for various reasons it maxes out at - 16TiB and won't mount any ext4 filesystem that's larger than this. As - of version 0.6.1, this driver supports the meta_bg feature, - which can also be used on ext2fs and ext3fs. Thus, it can handle some - ext2fs and ext3fs partitions that the ext2fs driver can't handle. You - can learn about your ext2/3/4 filesystem features by typing /boot partition and ext4fs on your root (/) + partition, to have the EFI scan only the former. This driver has some + limitations. Most notably, for various reasons it maxes out at 16TiB + and won't mount any ext4 filesystem that's larger than this. As of + version 0.6.1, this driver supports the meta_bg feature, which + can also be used on ext2fs and ext3fs. Thus, it can handle some ext2fs + and ext3fs partitions that the ext2fs driver can't handle. You can + learn about your ext2/3/4 filesystem features by typing dumpe2fs /dev/sda2 | grep features, changing /dev/sda2 to your filesystem's device.
  • Btrfs—Samuel Liao contributed this driver, which is based on the rEFIt/rEFInd driver framework and algorithms from the GRUB - 2.0 Btrfs driver. As of rEFInd 0.7.0, this driver is new and should be - considered experimental. 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 with a compressed Btrfs volume. I don't know if the driver will - handle other advanced Btrfs features, such as snapshots and - subvolumes.
    • + 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 + 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 + test installation of Ubuntu 14.04 alpha on such a system, I needed to + set also_scan_dirs + @/boot in refind.conf and add + rootflags=subvol=@ to the kernel options in my + refind_linux.conf file. Without the first of these options, + rEFInd could not locate my kernel; and without the second, the boot + failed with a message to the effect that the initial RAM disk could not + find /sbin/init.
  • ISO-9660—This driver originated with rEFIt's author, but he never released a final version. Its code was improved by Oracle for @@ -276,6 +283,8 @@ fs0: map -r