You have two options to switch to systemd-boot on Fedora:
Use inst.sdboot as kernel parameter while installing Fedora, see https://fedoraproject.org/wiki/Changes/cleanup_systemd_install
Or use conversation scripts systemd-boot-conversion provided by Sebastiaan Franken
I used the script for two of my installations without any issues: systemd-boot-install-fedora-no-secureboot.sh
Btrfs and subvolumes are your friends. See https://wiki.archlinux.org/title/btrfs#Subvolumes
This was already reported in https://github.com/TeamPiped/lemmy-piped-link-bot/issues/10 Latest commit seems to have broken the bot.
This is how we look down on the plebeians https://youtu.be/cUbri6sSgK4?si=lhyuA0M6__A70RBU or piped link https://piped.video/cUbri6sSgK4?si=WOm-6eAdWX_yEwwe
Relevant Youtube link: https://youtu.be/cUbri6sSgK4?si=WOm-6eAdWX_yEwwe
The accusation by Bryan is out there, its detailed and looks profounded - there is no response from SUSE anywhere and this seems to follow the described pattern in the accusation of not talking about it. So as of now the public opinion is that the accusation was not withdrawn and is still standing. Not talking about it won’t make it go away for anyone.
Same here. I have not heard anything after the initial accusations. The company I am working for is using SLES as a main OS and is switching to another OS without any explanation. So I have no idea if the claims are true or the switch has anything to do with anything.
Ubuntu because of forced Snaps
SUSE because of Yast and the (german) company’s rumored? stance on antisemitism (google banned Jewish holidays)
Fedora for it’s update mechanism with the forced reboot
Arch as the necessary evil
Issue still present after 30.0.1 update. One of the core features to send email shares is broken for more than a month. Not impressed at all.