Fedora Core Archive
This release is particularly exciting because it's the first to include the Fedora Modularity feature across all our different variants. Modularity lets us ship different versions of packages on the same Fedora base. This means you no longer need to make your whole OS upgrade decisions based on individual package versions. For example, you can choose Node.js version 8 or version 10, on either Fedora 28 or Fedora 29. Or you can choose between a version of Kubernetes which matches OpenShift Origin, and a module stream which follows the upstream.
You know where to get it.
A big project I've been working on recently for Fedora Workstation is what we call flickerfree boot. The idea here is that the firmware lights up the display in its native mode and no further modesets are done after that. Likewise there are also no unnecessary jarring graphical transitions.
Basically the machine boots up in UEFI mode, shows its vendor logo and then the screen keeps showing the vendor logo all the way to a smooth fade into the gdm screen.
People were complaining about this way back when I first actually got into Linux, somewhere in the early 2000s. I guess Fedora finally managed to get it working.
Fedora Workstation comes with two package managers by default: DNF and PackageKit. DNF has all the latest features and the best support, but PackageKit is put front and center in GNOME Software, KDE Plasma Discover, and as of Fedora 26 also in Cockpit’s new Software Update panel.
You may be better off sticking with the DNF package manager in the command line; even though PackageKit is the choice of all the graphical package managers. Here is some of the advantages DNF still gives you over PackageKit based applications.
Yes, after being pushed back from release after release, Fedora 25 finally defaults to using the Wayland graphics stack (assuming you have a supported graphics card). This is perhaps the biggest change to come in the Linux world since the move to systemd. However, unlike that systemd transition, the switch to Wayland was so seamless I had to logout and double check that I was in fact using Wayland.
I called Fedora 24, released earlier this year, "the year's best Linux distro" but one that I would have a hard time recommending thanks to some ugly kernel-related bugs. Well, Fedora 25 is here with an updated kernel, the bugs appear to be gone, and I have no reservations about recommending it. Not only is Fedora 25 a great release, the updated GNOME 3.22 running on top of Wayland appears to be slick and very stable.
The switch to Wayland has been so long in the making. That being said, I've been using Wayland for several years now - on my Jolla devices.
Like most Linux distros, Fedora is a massive, sprawling project. Frankly, it's sprawl-y to the point that it has felt unfocused and a bit lost at times. Just what is Fedora? The distro has served as a kind of showcase for GNOME 3 ever since GNOME 3 hit the beta stage. So Fedora in theory is meant to target everyday users, but at the same time the project pours tremendous energy into building developer tools like DevAssistant. Does that make Fedora a developer distro? A newbie-friendly GNOME showcase? A server distro? An obscure robotics distro?
Today, the answer to all the above questions is "yes." And the way to make sense of it all is what Fedora calls Fedora.Next.
/usr/bin, and all libraries to