Hi Andrei, Am 22.02.25 um 14:13 schrieb Andrei Borzenkov:
22.02.2025 12:16, Stefan Seyfried via openSUSE Factory wrote:
IIUC, e.g. blscfg on x86 is only possible with UEFI
That's incorrect as was already mentioned in this very discussion. grub2 does not care where boot entries come from as long as it can read them.
Ok, but probably not in a simple "no grub.cfg needed at all" configuration as seems to be envisioned for the UEFI case. (I know that it is possible, as it clearly is on RHEL's powerpc installation ;-)
As long as syslinux is still available and the kernel installation still creates a /boot/vmlinuz and /boot/initrd, we can always boot using extlinux from an ext3 partition or similar.
The challenge is not to load kernel but to maintain the list of available kernels. You can always set "no bootloader" in YaST Bootloader and install whatever you like; but it also stops refreshing your bootloader configuration on kernel installation/removal.
Yes, that's something that's simply not possbile anymore. Or has to be handled by the users on their own. It's no longer $YAST_SUCCESSOR's business. Maybe the linux kernel installation scripts could be amended to not only create "/boot/vmlinuz" symlink but also "vmlinuz.old" or similar, so that a static boot menu still could select the last boot entry. And if we want to go very fancy a static boot loader entry that loads a self-contained, ramdisk-only rescue system that allows to fix up bigger goofups could be developed by the community. Note I'm not advocating the "only UEFI is *supported*" way, but I can understand that for SLES at least, SUSE wants to extend the feature set in a specific way which might be incompatible with non-UEFI boot, so I'm thinking about how to keep the non-UEFI case still available for the community distributions without interfering too much with SUSEs goals. have fun, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman