summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorluxagraf <sng@luxagraf.net>2016-12-01 12:17:07 -0500
committerluxagraf <sng@luxagraf.net>2016-12-01 12:17:07 -0500
commita56dc6488b5810bd15c91b1c73ff329617e5ee07 (patch)
treed805d3463b92da9a149b95ec78a82f76b86dae3b
parentd7e4e7d47360a4db5e5e532150c3b1717fe5f064 (diff)
half way through fedora piece
-rw-r--r--fedora25.txt62
1 files changed, 62 insertions, 0 deletions
diff --git a/fedora25.txt b/fedora25.txt
index e69de29..b63c2f5 100644
--- a/fedora25.txt
+++ b/fedora25.txt
@@ -0,0 +1,62 @@
+The Fedora project has released Fedora 25, a major update for the Linux distribution.
+
+For the post several releases Fedora has been pursuing what it calls Fedora Next. Essentially Fedora Next took a step back and looked at how Fedora is used and came up with editions specifically tailored to those use case. The most notable of these are Fedora WorkStation and Fedora Server, which are the desktop/laptop and server versions respectively.
+
+Previous Fedora releases also had a "cloud" edition, but that's now been replaced by Fedora Atomic. Fedora Cloud, aside from having a meaningless name, didn't quite pan out. Since "cloud" is just a word for "someone else's server", it doesn't make much sense to release a "cloud" distro.
+
+What does make sense is to package up a version of Fedora specifically tailored for running container-based systems that uses a stable base system and the latest and greatest package. Using it is a bit like checking Fedora out from a Git repo. More on that in a minute.
+
+Interesting as Fedora Atomic is, much of the headlining news in Fedora 25 is in the WorkStation edition and can be summed up in a single word: Wayland.
+
+Yes, after being pushed back from release after release, Fedora 25 defaults to using Wayland (assuming you have a supported graphics card). This is perhaps the biggest change to come in the Linux world since the move to systemd, but unlike systemd the switch to Wayland was so seemless 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 problem recommending it. Not only is Fedora 25 an great release, the updated GNOME 3.22 running on top of Wayland is slick and very stable in my testing.
+
+## Wayland, New Kernel, and Updates
+
+The biggest change in this release is undoubtedly the move to Wayland as the default, erm, protocol, replacing the venerable X Server. Wayland's goal is to be easier to develop and maintain and, to a lesser degree, to get rid of the X's confusing clutter of accumulated bits that have been bolted on over the years.
+
+Wayland is not, strictly speaking, a display server like X. Wayland is a protocol for a compositor to talk through. To make things more confusing the compositor can be a Wayland client itself. It could also be an X application, some input device or a standalone display server. Wayland doesn't actually do much and that's by design. As the Wayland FAQ puts it, "the compositor sends input events to the clients. The clients render locally and then communicate video memory buffers and information about updates to those buffers back to the compositor."
+
+What's perhaps most remarkable for a change that's so low-level, and in fact one that's taking a lot of X functionality and moving lower down into the stack, is how unlikely you are to notice it. In my experience so far -- about two weeks of use as I write this -- the transition to Wayland has been totally transparent. Even better GNOME 3.22 feels considerable smoother with Wayland. It's difficult to describe without seeing it, but little moments of tearing that used to happen under X are gone and common tasks like dragging windows are much smoother.
+
+To be clear there are still plenty of things that don't work with Wayland. In fact there likely will always be legacy system element that don't know what to make of Wayland and will never be updated. For that situation there's XWayland, which is a plugin for Wayland compositors that runs a real X server inside Wayland. XWayland is big part of why you're unlikely to notice the move to Wayland.
+
+There are also some things to bear in mind about using Wayland with GNOME, more than few GNOME hacks won't work anymore. For example desktop icons, which aren't really a GNOME 3.x thing, though you could use Gnome Tweak Tool you can get them, are not supported in Wayland and never will be. I've also been unable to find a clipboard manager that works properly under Wayland.
+
+Those are, however, relatively minor issues. The biggest caveat to all the good news in Wayland is that Nvidia's proprietary driver does not support Wayland. The open source Nouveau drivers do, but those drivers can be a noticeable step down depending on your system and what you're trying to do. In my experience the Nouveau drivers are also a little buggy, though to be clear I haven't tested them with Wayland.
+
+Along with Wayland Fedora 25 brings Linux kernel 4.8.6, which means any lingering [Skylake bugs](https://bugzilla.redhat.com/show_bug.cgi?id=1353103) should be fixed. I tested Fedora 25 on the [Dell XPS 13](http://arstechnica.com/gadgets/2016/06/the-xps-13-de-dell-continues-to-build-a-reliable-linux-lineage/) I reviewed early for Ars and found Fedora 25 worked flawlessly.
+
+I should alos note that for the first time I was able to update from Fedora 24 to 25 using the GNOME Software system upgrade tool without any issues at all. That's a first for me in over ten years of using Fedora (to be fair most of that time I didn't even try because it was flat out hopeless) and goes a long way to making Fedora a distro that's friendly to less sophisticated users.
+
+In the past updating Fedora meant you'd need a few days to troubleshoot all the things that broke. It was a pain point that the project has been aware of and working on for some time. The nicely named FedUp tool arrived around Fedora 23, which helped some. Then the dnf upgrade tools came along in Fedora 24 and now there's a completely graphical upgrade path via GNOME software and perhaps most surprising, it just works.
+
+The only caveat I would add is that, like I imagine many Linux users do, I maintain an install of Fedora primarily to get a rough idea of what's coming in future CentOS releases. Which is to say that while Fedora gets a partition on my drive, I have not heavily customized it and don't have a ton of RPM Fusion repos installed, which could make for more problematic updates. Still, judging by comments sections, forums and posts around the web, my experience is not uncommon for the move from Fedora 24 to Fedora 25. That's not to say you're garanteed a smooth upgrade though. The real problem for most people seems to be with conflicting dependencies, often related to packages installed via RPM Fusion or other less-than-official repositories.
+
+My long standing criticism of Fedora is that major updates come too frequently for how terrible the updating process has been historically. Now that that seems to be changing and updates are smooth (and even have a nice GUI via GNOME Software) Fedora could start to find a wider audience.
+
+## GNOME 3.22
+
+GNOME 3.22 gnome has been a bot rough around the edges, development has finally gotten into its grove, shell extensions should continue to work as-is without breaking every extension with every release. Gnome as a stable thing
+
+Upgrading is an official thing
+
+
+
+## Fedora Next Next
+
+As mentioned above, Fedora Cloud is gone from the Fedora Next roster. Fedora Atomic edition is the replacement.
+
+Fedora Atomic takes the Fedora 25 base and functions a bit like Git -- you check out a particular point and that's the OS. Updates come every two weeks, which make it sort of rolling distro with snapshots.
+
+tk Why that matters
+
+To go along with Fedora Atomic. Docker support has also been expanded with a very cool looking tool that means users can build out images from t he base, using RPM-like tools. So the workflow becomes Fedora Atomic for your base, checked out identically across all your machines and then the expanded docker support gets your containerized apps installed.
+
+Fedora Server
+does not have a ton of new stuff -- for that you'll have to wait for Fedora 26, which will be an experimental release that ships with a lot more app already in containers.
+
+The SELinux management tool
+
+## Fedora Spins