Hopefully DNF5 gets in for F41, especially since it was supposed to get in as the default for the current release, F39. If anyone’s curious, here’s the vote for deferring: https://pagure.io/fesco/issue/3039

The reasoning for the upgrade: https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5#Benefit_to_Fedora

And the reasoning given by the DNF5 team for targeting F41 instead of F40: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/EYE2JY537OM7GFW46EK7YIBLHJ52USAZ/ (though fesco also wanted to keep it in F41 to not disturb the mass branching from F40 to RHEL 10)

And some things that need fixing before it becomes default: https://github.com/rpm-software-management/dnf5/issues/1057

And some commands that will be/are implemented: https://github.com/rpm-software-management/dnf5/issues/429

Personally, I just hope DNF4’s (what)provides comes back in full.

And they did, with bsdiff, an algorithm invented awhile ago. I wish system package managers carried this/weren’t actively dropping their implementations :(

The KDE packaging team is no longer packaging Xorg, but the GNOME team is. The “re-upstreaming” is a completely different effort with no guarantees on bugs. In addition, the package providing Xorg support in KDE is to be marked obsoleted and will be removed when upgrading. Here’s the actual ruling:

KDE packages which reintroduce support for X11 are allowed in the main Fedora repositories, however they may not be included by default on any release-blocking deliverable (ISO, image, etc.). The KDE SIG should provide a notice before major changes, but is not responsible for ensuring that these packages adapt.

GNOME Xorg still has full support from the team that has always worked on GNOME, unlike Plasma’s Xorg on Fedora 40.

No, it is not the same thing. From the Pagure issue:

From my recollection the WG earlier discussed about the removal of gnome-session-xsession, but we decided not to do that (wisely) until upstream drops it

It’s not like KDE, and when someone updates to F40, it won’t even remove Xorg. It just won’t be installed by anaconda by default in new installs.

Fedora has been a thing since 2003, released alongside Red Hat Enterprise Linux after Red Hat Linux was discontinued. The gaming issues sound interesting, though. Did you have steam installed through rpmfusion, flatpak, or something else?

It was available as a technology preview in RHEL 6 and 7, but dropped in 8. There apparently wasn’t much demand for it, and the reputation of BTRFS isn’t exactly synonymous with the image of reliability Red Hat strives for. There’s also the idea of maintenance and support burdens, and Red Hat themselves have launched their own stab at a fs with an integrated volume manager called Stratisd, though IBM supposedly absorbed the team that was working on it for their own products.

You wouldn’t use Silverblue on a server, you’d use Fedora CoreOS (FCOS) or CentOS Stream CoreOS (COSS). The ublue project has a FCOS derivative called ucore with options for ZFS OOTB. I use it on my server.

There’s some examples on how you’d use dockerfiles to build a ZFS module (as well as other things) from Fedora as well.

In any case, building bootable container images containing stuff like kernel modules is currently how this type of thing is done on atomic Fedora variants.

Fedora has another immutable variant for servers called CoreOS. It’s the default distro on any OKD cluster, though I run a derivative of it from ublue called ucore, which has a variant for zfs.

Looks like DDG appends “ - Red Hat” to search results under technology topics on RH’s website. Never noticed that, funny.