Talk:REFInd

Example configuration file location
Using 0.10.4-r1,

I found the refind.conf-sample file in /usr/share/refind-0.10.4/refind/refind.conf-sample, not /usr/share/doc/refind-*/refind.conf-sample. — The preceding unsigned comment was added by Russk (talk • contribs) 12 November 2016‎


 * Hi, Feel free to fix the path! It's a publicly editable wiki. Also, don't forget to sign you comments! :) --Maffblaster (talk) 17:40, 14 November 2016 (UTC)

Remove "Manual installation" section
It seems to me that the command works so well that there no need any longer for the "Manual installation" section. So I opt for deleting it. Any objections? --Charles17 (talk) 12:37, 15 June 2017 (UTC)


 * I can't really contribute much since I don't use refined, but if you say it works I think it's okay to remove the section. It sounds like it's deprecated anyway now that this bootloader has an installation command. --Maffblaster (talk) 16:24, 15 June 2017 (UTC)


 * Done. Who ever wants it back may get it from the older revisions.--Charles17 (talk) 07:24, 16 June 2017 (UTC)

Kernel management simplification
Using rEFInd for kernel management can be so much simpler than what is presented here:


 * 1) Leave the kernels (and initrd images, if they exist) in /boot, which is where "make install" (or genkernel) is going to install them anyway, and don't bother adding ".efi" extensions to the kernel names. If the user has followed the handbook instructions, /boot is the root of the EFI system partition (ESP), so rEFInd doesn't need to install any filesystem drivers to read it.
 * 2) Edit /boot/refind_linux.conf to pass a "root=" command line argument to the kernel so that the kernel knows where to find the root partition as it boots. 'echo \"Default\"  \"root=PARTUUID=partitionUUID\" > /boot/refind_linux.conf' would suffice for most people.
 * 3) Tell the user to hit  at the rEFInd boot screen to see the complete list of kernels available, which should be any kernel that has been dropped into /boot.

Note that this scheme is even simpler than using GRUB, since new kernels dropped into /boot will show up automatically, without needing to run a separate command akin to "grub-mkconfig". Having the kernels in /boot gives up the nice Gentoo logo (at least without some additional refind.conf configuration), but that seems like a small price to pay....

--G2boojum (talk) 22:20, 11 September 2017 (UTC)