this post was submitted on 28 Aug 2023
187 points (100.0% liked)
Linux
47918 readers
1184 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I love Universal Blue.
It's OCI cloud image based Fedora Silverblue/Kinoite/Serica with extra steps/batteries included.
But also probably an easier way for
Nvidia Fedorausers to game on Linux:Easily roll back deployments or 📌 one and rebase to something else easy peasy. (So many different choices) Test betas with no fear!
I've actually been gaming on Bazzite for two weeks now:
Jorge's Blog:
Media:
If you wanna simply make your own image to share with friends/family:
Universal Blue isn't a distro. It's more of a reimplementation/enhancement of ~~Immutable~~ OCI Cloud Based Images of Fedora.
People literally made a distro spin that's dedicated to rolling back nvidia drivers.
Classic nvidia moment right there.
But Universal Blue does look very interesting, I need to try and use it with distrobox and see if I can hit any walls that aren't there with a classic setup.
Nvidia is just a specific pain point, it's nice to be able to roll back to a specific version of any given deployment.
It's just more obvious for out-of-tree drivers since that's usually a worse user experience.
It does take some adjusting- the pitfalls you'd encounter with Distrobox on Universal Blue are the same as Distrobox on any other distro, so first I'd say to try moving your workflow to Flatpak and Distrobox on your current system or a VM and see how it works out. Generally Flatpak is preferred to a rootless Distrobox which is preferred to a rootful one, but sometimes there's not a Flatpak for something (especially command line tools) and you need access to hardware or system level stuff that only a rootful one can do properly.
Flatpaks are already my preferred way of installing random crap, but I did run into a few walls with that. VSCodium for example is unusable because it throws random errors about running out of space or not finding files that are definitely there even after giving it all the permissions via flatseal.
Proton has a similar thing where windows apps don't detect the amount of free space properly and see 4GB instead, so I guess it's inherent to containers.
I'll definitely try distrobox on my arch machine, is there anything I need to consider beforehand to not shoot myself in the foot?
Not particularly, the workflow on your Arch system will be the same as any other distro, that's the nice thing about Distrobox.
I would highly recommend looking into the
distrobox-assemblecommand, though: it lets you declaratively build distroboxes with the packages and config you need on them. I have a personal box which operates as my primary terminal that's automatically destroyed and recreated on every boot. This way, the packages I always use in a terminal are available, and I can add something I need temporarily with no issue without worrying about forgetting about that package being there down the line and causing some weird update failure or general bloat.uBlue is great. After using Fedora Silverblue for more than a year I used it to have the same OS on my laptop and desktop. It's works great and is quite simple if your already familiar with building containers. But the constant reboots and rebuilding an image taking minutes made me switch to NixOS.
The advantage of uBlue over NixOS is imo that the former is configured like any other Linux by placing files in the traditional file system hierarchy (e.g. binaries in /usr/local/bin). NixOS throws most of that over board and makes use of it's own configuration language and package manager. Getting started with uBlue is definitely easier, while NixOS is a time-consuming rabbit hole (not that uBlue isn't...). For a tiling wm setup I definitely think NixOS is the better choice, since changing core system components is quicker.
Here is an alternative Piped link(s): https://piped.video/watch?v=aaeRk8_i1Ds
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source, check me out at GitHub.