On Mon, Feb 17, 2025 at 5:45 AM Michael Chang <mchang@suse.com> wrote:
On Mon, Feb 17, 2025 at 04:51:55AM -0500, Neal Gompa wrote:
On Mon, Feb 17, 2025 at 3:29 AM Thorsten Kukuk via openSUSE Factory <factory@lists.opensuse.org> wrote:
On Mon, Feb 17, 2025 at 8:46 AM Stefan Seyfried via openSUSE Factory <factory@lists.opensuse.org> wrote:
Am 17.02.25 um 08:25 schrieb Michael Chang:
We take a different approach than RHEL by putting all BLS config, along with the kernel and initrd, in the EFI partition (/boot/efi) instead of /boot. Also, grub.cfg is not used at all. It is basically the same layout you would have with systemd-boot, just a different loader can be an option.
So SLES powerpc will boot with something else than grub? Or will powerpc also get an ESP?
The company behind POWER does not want to support BLS, so everything stays the same. And since there is currently no technical need for BLS on POWER, this is not a problem. Interesting is that RedHat as part of this company seems to introduce BLS on this architecture...
This seems strangely false, since IBM introduced BLS support to zipl years ago. On Red Hat/Fedora systems, BLS is used with GRUB, petitboot, and zipl. Petitboot knows how to handle BLS with GRUB on POWER just fine.
There are several differences, but the main one is that Fedora/Red Hat use /boot for blscfg, whereas we use /boot/efi. As a result, they do not require an additional ESP-like partition on Power for integration.
Additionally, Fedora/Red Hat still use /boot/grub2/grub.cfg alongside blscfg, with Linux entries replaced by blscfg commands that retrieve BLS fragments from /boot/loader/entries/. In contrast, our scheme eliminates grub.cfg entirely (as that is a bloat).
Moreover, while Fedora/Red Hat store kernel and initrd in /boot, we need to copy them to /boot/efi.
There are people in Fedora who want to put everything in the ESP, but there are many (including myself) who think it's a terrible idea. The ESP can only get so big before various systems fail to be able to read it, and not all firmwares even handle a FAT32 ESP either. I think you're making a mistake by doing it this way, as now the OS is more vulnerable to host firmware goofiness. Considering /boot as bloat seems silly since we do this specifically to avoid the restrictions of the underlying platform. The grub.cfg file is more of an installation difference. Anaconda generates the config file as part of installation. -- 真実はいつも一つ！/ Always, there's only one truth!