Compared to GRUB, these points spring to mind concerning rEFInd: That said, there are advantages and disadvantages to any piece of software, including boot loaders. (There are occasional exceptions to this rule, but as I said, they're rare.) Thus, if rEFInd boots your system, you needn't worry too much about follow-on problems. It's rare to experience post-boot problems with any boot loader once the kernel boots, it either works completely or not at all. (I forked rEFIt into rEFInd because I dislike GRUB 2 and I thought much of what rEFIt did was elegant, but not quite what I needed.) I maintain rEFInd, so I understand how it works and interacts with Ubuntu pretty well but I'm also not without my own biases and preferences.
Lastly, does this guide look reliable?ĮDIT - unlike other pre-existing ones, the focus of this question is on Windows-Linux dual boot (although the answer below seems to cover any OS, with focus on Debian-based ones). What I'm worried about are the possible downsides, especially whether a fancier bootloader like rEFInd might slow down my boot process. I'm currently using GRUB, but planning on switching to rEFInd, mostly for the eye-candy.
I have a machine with an Ubuntu derivative dual booted with Windows 10. efi file) just add the line dont_scan_dirs EFI/boot,EFI/Dell,EFI/memtest86. If you still see useless entries (I had one which said "fallback boot loader etc" without specifying any. FINAL EDIT - If you are planning on installing rEFInd you might want to read Rod's answer below.Īfter installing if you have a bunch of useless entries just write down their name on a piece of paper (rEFInd will describe them as somefile.efi), then open nf and add the line dont_scan_files somefile.efi,someotherfile.efi