+ <tt>initrd-4.2.5-300.fc23.x86_64.img</tt>. In order to support Arch Linux
+ kernel naming the strings <tt>linux</tt> and <tt>linux-lts</tt> are
+ treated as digits. So <tt>vmlinuz-linux-lts</tt> has version
+ <tt>linux-lts</tt>, which matches <tt>initramfs-linux-lts.img</tt>.
+ Many other matches are possible. If an initial RAM disk is identified,
+ rEFInd passes a suitable <tt>initrd=</tt> option to the kernel when it
+ boots. There are two variants on this rule:
+
+ <ul>
+
+ <li>As an extension to the preceding point, if multiple initial RAM disk
+ files match one kernel, the one whose filename matches the most
+ characters after the version string is used. For instance, suppose
+ the kernel filename is <tt>vmlinuz-4.8.0-32-standard</tt>, and two
+ initial RAM disk files are <tt>initrd-4.8.0-32-standard</tt> and
+ <tt>initrd-4.8.0-32-debug</tt>. The first of those files has nine
+ matching characters after the version string (<tt>-standard</tt>),
+ vs. just one matching character (<tt>-</tt>) for the second. Thus,
+ the first file will be used.</li>
+
+ <li>If the <tt>refind_linux.conf</tt> file (described next) is present,
+ and if an <tt>initrd=</tt> specification is present for the option
+ you're using, rEFInd will <i>not</i> add a pointer to the initial
+ RAM disk file that it discovers. This feature enables you to
+ override rEFInd's initial RAM disk discovery. This is most useful in
+ Arch Linux, which can be configured with two different initial RAM
+ disk files, one to be used for normal booting and one for recovery
+ situations. You can specify each initial RAM disk file on its own
+ line, which gives you the ability to control which to use at boot
+ time.</li></ul>