Fedora Kinoite vs. Silverblue: My verdict after testing both immutable Linux distros


Fedora Kinoite vs. Silverblue

Fedora and Silverblue

Follow ZDNET: Add us as a preferred source on Google.


ZDNET’s key takeaways

  • Silverblue and Kinoite are atomic/immutable Linux distributions.
  • Silverblue uses GNOME, while Kinoite uses KDE Plasma.
  • Both are highly secure and reliable desktop operating systems.

Immutable Linux distributions are slowly becoming more popular. Given the rise in discovered vulnerabilities, any additional security you can get is a bonus.

For those who don’t know, an immutable Linux distribution is one that mounts certain directories, such as /usr, /var, and /etc, as read-only so they cannot be changed. That’s a good thing.

Also: Fedora 44 made me forget I was using Linux – in the best way

The developers of Fedora Linux understand this and have developed a distribution called Silverblue. From that distribution came Kinoite

What’s the difference?

As I’ve said, these are both immutable, so the underpinnings are the same. The differences lie on the desktop side. Let’s dive in and see which one of these is best suited for you.

What is Fedora Kinoite?

Fedora Kinoite

The Kinoite desktop is as elegant as it is user-friendly.

Jack Wallen/ZDNET

Fedora Kinoite is the atomic/immutable Fedora distribution dedicated to KDE Plasma. You get the same immutable base (and the atomic updates), but with a more traditional desktop environment on top. Of course, KDE Plasma is much more than a “traditional” desktop. After all, this is Linux, and Linux doesn’t always follow the rules.

Why KDE Plasma?

One of the reasons why KDE Plasma is so popular is that it doesn’t require users coming from Windows to think too hard to work with the desktop. There’s a bottom panel, a desktop menu, a system tray, quick launch icons… all of the things you’re used to on a desktop.

Also: Your KDE Plasma desktop is about to get a huge upgrade with 6.6 – what’s inside

KDE Plasma is still Linux, so it’s highly customizable. Without much effort, you can make the desktop look and feel exactly how you want. Or, you can leave it as is and just enjoy all of the beauty that comes with the default settings.

I could end it there, simply by saying it’s immutable Fedora with a KDE Plasma desktop, but that’s no fun.

Also: The best Linux laptops

Let me talk about why I think KDE Plasma and immutable Fedora make a great pair.

When you open KDE Discover (the KDE Plasma app store), you can search for any apps you’d like to install. But this is where it could get tricky (especially if you’re curious). 

Fedora Kinoite

You have to manually add the Flathub repository for KDE Discover.

Jack Wallen/ZDNET

Let’s say you want to install LibreOffice. You can search for LibreOffice and click the install button. The installation will happen, even without you having to type your user password. If you look closely at the settings, however, you’ll find that Flathub isn’t enabled by default, so LibreOffice is installed from the Fedora repositories. That sparked my curiosity, so I opened the terminal window and typed:

rpm -qa libreoffice

Nothing.

Next, I ran the list option with Flatpak like so:

flatpak list

There it was: org.libreoffice.LibreOffice.

Even though Flathub wasn’t enabled by default, KDE Discover installed Flatpak apps from the Fedora repository. I then downloaded the RPM files to install LibreOffice, only to find that /usr/share/rpm was locked.

I then enabled Flathub in KDE Discover > Settings > Add Flathub. Once that was taken care of, the list of available apps grew exponentially.

Because this is an immutable distribution, apps must be installed via containers (such as Flatpak); otherwise, those directories that are mounted read-only would have to be mounted with write permissions, thereby defeating the purpose of immutability.

What this does is give you a KDE Plasma experience that is far more secure than it might otherwise be. If you’ve ever compared Flatpak apps against native apps (such as Fedora .rpm), you know that 1) the installation takes a bit longer and 2) apps don’t start quite as quickly.

Also: Want to save your aging computer? Try these 5 Linux distributions

Is the added security worth the extra time? It most certainly is. And because KDE Plasma is already a fast and efficient desktop, the extra time is negligible. 

Who is Fedora Kinoite for?

Fedora Kinoite is for anyone who wants the KDE Plasma desktop but would also enjoy the added benefit of an immutable distribution. Easy peasy.

Oh, but there’s more. Because of how Fedora’s immutable distributions are created, you can do what’s called “rebasing,” which essentially allows you to switch between versions. Let’s say you’d like to try COSMIC desktop. You could do that with the command:

rpm-ostree rebase fedora:fedora/44/x86_64/cosmic-atomic

The process takes a bit of time, but it’s pretty cool. When it completes, reboot with the command systemctl reboot, and you’ll be greeted by the COSMIC desktop.

But we’re talking about KDE Plasma, so you might not want to rebase until you’ve given the default desktop plenty of time.

What is Fedora Silverblue?

Fedora Silverblue.

GNOME is minimal, but that doesn’t mean it’s without all the features you need.

Jack Wallen/ZDNET

Silverblue is to GNOME what Kinoite is to KDE Plasma. However, Kinoite is not a rebase of Silverblue. However, you could rebase Silverblue to KDE Plasma if you wanted, but if you want to do that, just go with Kinoite.

Confused yet?

Don’t be. All you have to do is remember that Fedora Silverblue is the atomic/immutable version with the GNOME desktop.

Also: You can use Linux 7.0 on these 7 distros today – here’s what to expect

Why GNOME?

If you prefer your desktops to be minimal and get out of your way, then GNOME is what you want. GNOME isn’t for everyone. If you like the typical Windows layout, you’ll find GNOME to be problematic. Yes, you can install GNOME extensions to make it a bit more Windows-like (or very Windows-like if you prefer), but GNOME is all about simplicity, and it achieves that quite well.

Silverblue enjoys all of the bells and whistles found in Kinoite, so you get the immutable file system for security and the atomic updates (which ensure that if there’s a problem with an update, the system will not proceed, so Linux always works). 

There is one difference. With Silverblue, you don’t have to enable Flathub support in the app store. When you go to install an application, you can select between the Fedora and the Flathub repositories out of the box. That’s an important distinction, especially for those who don’t want to have to take the extra steps to add Flathub repositories.

Fedora Silverblue.

GNOME Software ships with Flathub support enabled.

Jack Wallen/ZDNET

Who is Silverblue for?

With Silverblue, you get the immutable file system, atomic upgrades, GNOME desktop (and everything that comes with it), as well as the Flathub repositories enabled by default.

Also: GNOME 50 is a brilliant release – but I had to look twice to see why

To that end, Silverblue is for those who want a minimal desktop that gets out of their way, want the added security and reliability of an atomic/immutable OS, and don’t want to have to set up the app store to pull apps from the Flathub repositories.

Which is right for you?

In the end, it boils down to this: Do you want the KDE Plasma desktop or the GNOME desktop? Make that choice, and you’ll know exactly which version is right for you. Either way you go, you’ll get the same reliable/secure OS with the speed and power of Fedora Linux.





Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


When you pick out a phone, you’re also picking out the operating system—that typically means Android or iOS. What if a phone didn’t follow those rules? What if it could run any OS you wanted? This is the story of the legendary HTC HD2.

Microsoft makes a mess with Windows Mobile

The HD2 arrives at an unfortunate time

windows mobile 6.5 Credit: Pocketnow

Officially, the HTC HD2 (HTC Leo) launched in November 2009 with Windows Mobile 6.5. Microsoft had already been working on Windows Phone for a few years at this point, and it was planned to be released in 2009. However, multiple delays forced Microsoft to release Windows Mobile 6.5 as a stopgap update to Windows Mobile 6.1.

Microsoft’s plan for mobile devices was a mess at this time. The HD2 didn’t launch in North America until March 2010—one month after Windows Phone 7 had been announced at Mobile World Congress. Originally, the HD2 was supposed to be upgraded to Windows Phone 7, but Microsoft later decided no Windows Mobile devices would get the new OS.

This left the HD2 stuck between a rock and a hard place. Launched as the final curtain was dropping on one OS, but too early to be upgraded to the next OS. Thankfully, HTC was not just any manufacturer, and the HD2 was not just any phone.

The HD2 was better than it had any right to be

HTC made a beast of a phone

HTC HD2 Credit: HTC

HTC was one of the best smartphone manufacturers of the late 2000s and 2010s. It manufactured the first Android phone, the first Google Pixel phone, and several of the most iconic smartphones of the last two decades. Much of the company’s reputation for premium, high-quality hardware stems from the HD2.

The HD2 was the first smartphone with a 4.3-inch touchscreen—considered huge at the time—and one of the first smartphones with a 1 GHz Qualcomm Snapdragon processor. That processor, along with 512GB of RAM, made the HD2 more future-proof than HTC probably ever intended. Phones would be launching with those same specs for the next couple of years.

For all intents and purposes, the HD2 was the most powerful phone on the market. It just so happened to run the most limiting mobile OS of the time. If the software situation could be improved, there was clearly tons of potential.

The phone that could do it all

Android, Windows Phone, Ubuntu, and more

The key to the HD2’s hackability was HTC’s open design philosophy. It had an easily unlockable bootloader, and it could boot operating systems from the NAND flash and SD cards.

First, the community took to righting a wrong and bringing Windows Phone 7 to the HD2. This was thanks to a custom bootloader called “MAGLDR”—Windows Phone 7.5 and 8 would eventually get ported, too. The floodgates had opened, and Windows Phone was the least of what this beast of a phone could do.

Android on the HTC HD2? No problem. Name a version of the OS, and the HD2 had a port of it: 2.2 Froyo, 2.3 Gingerbread, 4.0 Ice Cream Sandwich, 4.1/2/3 Jelly Bean, 4.4 Kitkat, 5.0 Lollipop, 6.0 Marshmallow, 7.0 Nougat, and 8.1 Oreo. Yes, the HD2 was still getting ports seven years after it launched.

But why stop at Android? The HD2 was ripe for all sorts of Linux builds. Ubuntu—including Ubuntu Touch—, Debian, Firefox OS, and Nokia’s MeeGo were ported as well. The cool thing about the HD2 was that it could dual-boot OS’. You didn’t have to commit to just one system at a time. It was truly like having a PC in your pocket, and the tech community loved it.

Do a web search for “HTC HD2” now, and you’ll find many articles about the phone getting yet another port of an OS. It became a running joke that the HD2 would get new versions of Android before officially supported Android phones did. People called it “the phone that refuses to die,” but it was the community that kept it alive.

The last of its kind

“They don’t make ‘em like they used to”

HTC HD2 close up Credit: TechRepublic

The HTC HD2 was a phone from a very different time. It may have gotten more headlines, but there were plenty of other phones being heavily modded and unofficially upgraded back then. Unlockable bootloaders were much more common, and that created opportunities for enthusiasts.

I can attest to how different it was in the early years of the smartphone boom. My first smartphone was another HTC device, the DROID Eris from Verizon. I have fond memories of scouring the XDA-Developers forums for custom ROMs and installing the latest Kaos builds on a whim during college lectures. Sadly, it’s been many years since I attempted that level of customization.

It’s not all doom and gloom for modern smartphones, though. Long-term support has gotten considerably better than it was back in 2010. As mentioned, the HD2 never officially received Windows Phone 7, and it never got any other updates, either. My DROID Eris stopped getting updates a mere eight months after release.

Compare that to phones such as the Samsung Galaxy S26, Google Pixel 10, and iPhone 17, which will all be supported through 2032. You may not be able to dual-boot a completely different OS on these phones, but they won’t be dead in the water in less than a year. We will likely never see a phone like the HTC HD2 from a major manufacturer again.

HTC Droid Eris


A Love Letter to My First Smartphone, the HTC Droid Eris

No, not that DROID.



Source link