24
Linux way way slower than Windows?
(lemmy.ca)
Gaming on the GNU/Linux operating system.
Recommended news sources:
Related chat:
Related Communities:
Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.
Exactly.
So as an explanation, Fedora Atomic is like Git for your OS. This means the OS keeps track of every package, what is where etc. On the server lays a fresh, recent image, assembled by the Fedora people. They ship really recent software and these images are well tested and should just work.
This is exactly the state you have on a regular Distro, after installing the ISO (and nothing went wrong). But what happens now? You install, uninstall, move, compile, write stuff to system directories, etc.
In the end we have 100 Ubuntu users with 100 different systems. "I have this issue but nobody else has it", yes because your system is unique and you have no idea why.
Meanwhile Android does the exact opposite, since forever. And that sucks. But as apps are highly confined and the system is read-only (lol often not even readable) you have no viruses.
Fedora Atomic with rpm-ostree does a thing in between. You have your Operating system, good as it is. But in Fedora for example there are Codecs missing so Firefox or direct Binaries like Davinci Resolve will give you a hard time.
You can "layer" packages though, that means from then on you have the official image plus a transparent set of extra packages. If you find out this breaks something, do
rpm-ostree uninstall PACKAGE
and that layer is gone.If you want to reset your system entirely, do
rpm-ostree reset
(this is not android-level yet, you still need to remove /var /etc and more.)Also there are containers. They are not virtual machines because they use your systems kernel. But you can install all those nasty dependencies you need for example for that one old app, for building software etc. Using Toolbox or Distrobox this is really easy.
So before modifying the system, you can use that instead. Still, you can modify your system a lot, add repos, etc.
Then comes universalBlue. They do the modifying BEFORE sending the images to your client. So the modifications are not your own, and errors may already be discovered when you would get them. Also, having the changes there reduces the load on your machine, all you do is download, build, reboot, done. Automatically.
This is so much better than Windowd Updates, more secure and with no boot delay AT ALL. That fact alone is a crazy selling point.
If you ask yourself "why should I need this", just think about how your OS will look like in 5 years. So many changes, but using rpm-ostree you are always just one command away from having a "fresh install" experience.
Incredible tech huh? I'd toyed with the idea of immutable distros before with NixOS but found it a bit too restrictive so Kinoite and co are exactly the middle ground I was looking for.
With Bazzite specifically, I get a pretty damn up to date Fedora base, most of the annoying kernel/gaming things I want but don't want to mess with by default and also Nix + distrobox out of the box for development environments and some wiggle room for whatever I can't natively install. Just a great experience all around.
Wait Nix is on there?
Yup! I've deployed my Home Manager config on my install with no issues.
Thanks for the thorough explanation, Fedora atomic, os-tree and Universal blue is such a new and different way of thinking about the OS compared to the traditional desktop installs. It's also a lot of new jargon so thanks for taking the time to explain each component
Fedora Podcast about Silverblue with Timothee Ravier and Jorge Castro
Linux User Space Podcast talking about the ENTIRE history of Fedora Atomic, and different "immutable" models
Do you or anyone else know how MicroOS compares to that? I know that it's mostly the same technology and I preferred Tumbleweed over Fedora Workstation
As far as I understood its worse, as they dont use OSTree but BTRFS snapshots. So they have an image, do atomic updates from some repository (not sure how thats done) and then build the next image. This process is atomic as a fail will cancel the update.
But the fetching or things is done via a normal package manager, its just building differently on your machine, again, aa far as I understood.
Then you have BTRFS snapshots which you reboot into. You can also layer packages, not sure how that is done and if its reversible.