brew install gdu

Hi I work on bluefin, it's impossible to tell what the problem is without reading the error you received.

We don't claim it's unbreakable (or immutable) it just means you have a better chance of an upgrade working that day vs. what it replaces. There's still tons of places for things to go wrong, boot loader, etc. If you have the error log somewhere I can take a look.

This is awesome! I'll add this to bluefin server! Thanks!

You will find more support online for Fedora Silverblue/Kinoite over Bluefin.

And we will be the first to tell you that most of that doesn't apply.

bootc update is one command? No grub in dakotaraptor you can build right from bst with systemd-boot.

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. (system upgrades should work, app installation shouldn't break the PC, etc.)

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 there are people that claim they need super technical things like virt-manager on the image and yet can't manage a simple linux service. "Forced Updates". Images like Bazzite are the antithesis for people who want to be experts without putting in the work.

The entire bazzite build process is well documented, the entire pipeline is implemented with standard CNCF and OpenSSF tooling, the readme has crypto verification that you can run to verify it yourself. These systems have been in place since before Universal Blue went GA (It's about 5y old).

Fedora being a better choice than Homebrew because it's update pipeline is too slow is not something anyone should be proud of. The Bazzite images run full syft scans before they're even finally assembled, if it's in there that second the build fails and users never see it. The entire industry is moving left on this, with proactive work upstream - "keep old things in the field" is an antipattern.

Here's all the info!

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.