this post was submitted on 06 Sep 2025
116 points (98.3% liked)

Linux

13108 readers
100 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] floofloof@lemmy.ca 6 points 1 week ago* (last edited 1 week ago)

Well, only the base OS in /usr is immutable; /etc is writable for making system-level config changes, and your entire home folder is of course yours to do what you want with, including installing software into it. So that’s what you do: use Discover to get software, mostly from Flathub at this point in time, but Snap is also technically supported and you can use snap in a terminal window (support in Discover may arrive later).

That’s fine for apps in Flathub and the Snap Store, but what about software not available there? What about CLI tools and development libraries?

Containers offer a modern approach: essentially you download a tiny tiny Linux-based OS into a container, and then you can install whatever that OS’s own package management system provides into the container. KDE Linux ships with support for Distrobox and Toolbx.

It sounds like more work for the user than a single system-wide package manager. And in my experience there are some applications that are not designed for sandboxed installations, where you have to fiddle around with the sandbox settings to get things to work. I've become frustrated by this in the past and ended up going back to system-level, unsandboxed packages. Likewise, managing containers for CLI applications can be great or it can be a pain for similar reasons. Some things are just easiest when fully integrated with the OS, though it brings security and stability risks. So I haven't been won over by immutable distros yet but I'll be interested to see whether KDE Linux can soften some of these hard edges for the user. It sounds like they do want it to be viable for non-experts coming from Windows.