j0rge

It is 100% possible and people have been doing it for years. If the package is broken the final product is never built, it’s impossible to ship it to the end user since it’s one whole complete image.

Because the image never gets built if there’s a packaging error, so the user never ends up on a broken image. A broken package never makes it to the end. If it’s broken the user just doesn’t get an image until the package is fixed and then they get a new image.

Updates can be ensured and broken repositories go away entirely that’s the entire point. I don’t think it’s “nice” I would consider that a basic feature in Linux. If you like Linux your way then that doesn’t go away.

I still miss the advantages for these cases. Zero-maintenance and upgrades. Update it every once in a while or setup auto updates. I do not see any difference between traditional os and immutable. You’re likely not modifying any system files anyway. You’re overthinking it, there’s no reason to care if the root disk is readable or not. If it updates reliably out of the box there’s no reason to touch it. Are they really going to brick their system? That would require opening the terminal. But I mean, fair. You don’t need to open a terminal to brick a traditional linux system they tend to do that on their own. What I do not understand is why there are users swearing by bazzite and other immutable distributions. These examples you make is basically for users who just do the most basic operations with their systems. I can’t speak for “immutable distributions” but for bazzite it’s to ensure working upgrades. What I do not understand is why technically adept people are so excited for these kinds of distributions? I’m technically adept at Linux I expect software to work.

This is pure operator error, all of these systems are well documented and are literally linux 101. If the response is “how are normal users supposed to?” the answer is normal users don’t use command line tools. The person saying that they’re switching to Kinoite is in for a rude surprise when they find out that the virt-manager flatpak everyone is migrating to is written and maintained by the Kinoite maintainer, we helped with the QEMU extension because moving this stuff to userspace is something everyone agrees on. Hopefully you’ve learned that people that claim they need super technical things like virt-manager on the image can’t manage a simple linux service and tell you they’re locked in. Images like Bazzite are the antithesis for people who want to be experts without putting in the work.

Hah yeah I spoke to Jon about this stuff at KubeCon. I said something like “Try to keep up!” :) Lots of common tooling in this space though and getting more attention to open models can only help.

The terminal motd tells you exactly how to use the packages involved when you open it.

Just about everyone who has made meaningful contributions to Bluefin are tinkerers. The entire stack is designed to tinker and customize.

It’s one command in Bluefin, same as everything else.

brew install btop vim docs.projectbluefin.io/command-line/#installing-a…

I feel like they don’t take the time to think things through and throw together. Instead, they throw together a new thing to address the shortcomings of the previous five things. This is a weird statement it’s designed this way on purpose. You seem to be looking for “one package manager to rule them all” in a world that’s purposely splitting things up.