https://bugzilla.suse.com/show_bug.cgi?id=1226122 https://bugzilla.suse.com/show_bug.cgi?id=1226122#c59 --- Comment #59 from Mario Guzman <mario_bz@mgtech.com> --- I have detailed the issues in my comments above. Here is a summary of some of the items I mentioned above: First, this is all solved by simply implementing a legacy/compatibility option for booting in the installer. Keep /boot as is for people who want need it. It's been working all these year so why not allow it as an option. 1. sdboot (and grub) is useless to me. I am not just multi booting multiple Opensuses, but multiple type of operating systems. One my main development system I have three Opensuse and two other Linux systems, and 3 macOS systems. sdboot is only for a specific instance of linux. 2. On some older systems I use the Open Core Legacy Patcher booter to allow newer macOSs to run on unsupported systems. OLCP resides along side Refind Plus perfectly. sdboot is useless in this case. 3. sdboot requires an ESP partition to put the kernel AND a configuration file for EACH kernel. So if I want to keep everything completely independent I need an ESP partition for EACH Opensuse. I had five at one time, so that would require 10 partitions for five Opensuse systems! Partitioning becomes a nightmare. It seems sdboot assumes people will have one and only one OS, like Windows! 4.sdboot requires a configuration file for each linux. Wow, Refind requires nothing, I can install Opensuse without a boot manager, and immediately boot it with no configuration. Simplifies new installs AND nothing to do when the kernel is updated. Refind finds everything automagically. So in my case, sdboot would do nothing but get in the way and prevent multi boot of various systems, and add work since it needs configuration changes for every kernel update. It sounds like Refind may boot into sdboot is possible, then chain to linux. But why add the maintenance of configuration file and slow down boot when all we need for simple multi boot systems is to keep /boot populated as it is now. Please, just add a compat/legace option to load /boot and not install a boot manager. I know it's easy because I just added the missing boot installer script and everything works as before. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.