openSUSE Tumbleweed Forces systemd-boot Shift; Arch Users Grapple with Mount Point Abyss
openSUSE Tumbleweed is shifting its default bootloader to systemd-boot. This transition forces immediate technical friction, particularly concerning the EFI System Partition (ESP) mount point setup within Arch Linux environments.
The technical justification for this move is heavily contested. While some accept the change as policy, others, like 'sakphul', demand deeper technical grounding, stating linked blog posts are insufficient and the official mailing list holds the real rationale. Meanwhile, 'Nicro' details the practical failure point: package configs assume the ESP is at /boot, conflicting with a desired /boot/efi mount structure. To complicate matters, 'bjoern_tantau' intervened to clarify that systemd-boot itself functions independently of the broader systemd suite.
The core conflict centers on configuration rigidity versus modern best practice. The consensus is on the functional difficulty of handling the ESP mount point—whether /boot or /boot/efi—while the technical support for Tumbleweed’s mandate remains fractured, requiring users to dig into official mailing archives for concrete answers.
Key Points
openSUSE Tumbleweed is adopting systemd-boot as its default bootloader.
The change is stated as fact by some, but the technical basis is disputed, pushing discussion to the official mailing lists rather than blog posts.
Arch Linux users cannot reconcile systemd-boot setup with canonical mount points.
'Nicro' reports package configurations are hardcoded assuming /boot for the ESP, conflicting with the preferred /boot/efi mount.
Systemd-boot's functionality is not tied to the wider systemd suite.
'bjoern_tantau' asserts systemd-boot is architecturally independent, a key clarification for system integrity.
External documentation is insufficient for understanding the rationale.
'sakphul' explicitly dismisses linked blog posts, demanding the technical details come directly from the official OpenSUSE mailing list.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.