Linux distro's heading to where macOS today: where the root filesystem is mostly immutable, but not entirely. #ChromeOS arrived there a decade ago, but everyone seems to be moving in the same direction.
We're FINALLY doin it again. Livestreamin' that is.
Come join us and laugh at how badly the #Gentoo journey will go. And while we're waiting for compiles, we'll be on the other side of the spectrum with composables? immutables? image based? whaaaa?
Here's a Flatpak story: The other day, my best friend told me that he had switched to Linux! Arch Linux with KDE Plasma, a noble choice in my opinion. He's a smart guy, but he was having some issues that he couldn't figure out: Firefox' maximise and minimise buttons were missing, drag and drop from archives wasn't working, his selected theme wasn't applied everywhere, and many other small issues I can't remember now.
I tried reproducing his issues on my machine, but everything worked fine for me. We were confused. Is there missing libraries? We went through packages to find out what my system had that his didn't. It was weird, everything was kinda working, but the devil was always in the details, for every single app.
And then we found it: All those applications he had issues with were Flatpaks! He simply didn't pay attention when installing them through the Discover store. He didn't even know what Flatpak meant.
I helped him remove Flatpak from his system and install the system packages instead, and all issues were gone.
Man, Flatpaks suck. How does anyone prefer Flatpaks over system packages? How does anyone think this was a good idea? Stop trying to invent new things to solve old problems and instead go back and fix the problems.
Containers, Flatpak, Immutable distros, it's all wasted effort. There is no magical solution that will solve all our problems. The only way to solve all problems is by solving each problem individually one by one. And that is exactly what countless distribution and package maintainers are doing on your behalf every single day.
Hello fedi! I'm making my own immutable distro, and I've got some questions:
what should I use to build? I was thinking bluebuild hut it might be more trouble than it saves, as I need to do stuff like add an extra btrfs subvolume on install, and I'd like a custom gtk4 installer.
other than that, assuming I use bluebuild for now, would a structure like this work?
core - has core system stuff, like kernel, bootloader, etc. Included in image, needs reboot to apply
other/system - has other stuff like system flatpaks, config files, anything that doesn't need a reboot to change
Each would be cached so only core or other would be rebuilt depending on the last value.
other would use an overlay inside a btrfs sub volume. I was thinking I apply changes directly to the subvolume and rollback if they interrupt or an error occurs, but now I'm thinking a power cut or other force shutdown might mess that up.
Any thoughts would be appreciated, thanks! You're helping to shape QuadOS! QuadOS currently has the following devs: Me, @Heliguy, and @winsdominoes. It aims to be like NixOS, but using flatpaks, and hopefully less janky.
Today in User Space
📈We enable MORE #telemetry
🐧Get enticed by #immutable distros
📖Look back into our own personal #history
🗒️Fall down the #notes rabbit hole
🎨And add a splash of color to our #CLI
This week, Jonathan Bennett and Dan Lynch talk with Shawn W Dunn about openSUSE Kalpa, the atomic version of openSUSE Tumbleweed, with a KDE twist. What exactly do we mean by an Atomic desktop? Is …
As I ordered a #laptop after years of struggle (#Asus TUF A16 from #2023), it's likely I will need a new #Linux#distro. Which apparently brings us to the #2024 Best General Use #OS#Competition! Please meet our contestants:
#Windows 11 – the most popular OS on market. But is it really good? Unlikely.
#LinuxMint Cinnamon Edge – in my experience the best by far, intuitive, just works and never gets in your way. But can it handle a laptop that's not even a year old?
For users of any operating system, not just #Linux, what might keep you from trying/running an #immutable#Fedora desktop? If you are already running one, why did you choose it?
Do you wish you could run #Linux on an ASUS ROG or whatever your current #gaming rig is, but not sure where to start? Then check out #Bazzite! It is an #immutable Linux distro based on #Fedora Atomic from the #UBlue group so you can focus more on gaming and less on being a sys admin for your gaming gear!
Jesus fucking Christ, if users of #immutable#Linux distros aren't just the most insufferable people on the goddamned planet. The absolute epitome of the pathetic "excuse me, but I use Linux, BTW" type of "personality" that literally everyone hates.
Every possible moment they can mention it, every single thread, every fucking day.
No one, and I mean literally no one other than your little online "friends" cares about whether or not you use fucking #Silverblue or #NixOS.
I'm curious what the book said the use case for that was 😀
[:] makes a #copy of the entire string - or other #sequence. But strings in Python are #immutable; if you just do stringA = stringB, you'll get exactly the same behaviour - if someone else "modifies" B, they're actually creating a new object, and stringA will still refer to the original.
Copying a substring with [x:y] (optionally omitting one of them) is common and useful. But the whole thing... ?
Last night, my personal computer lost power while doing a package update. Unbootable, ofc. So I boot up a live iso, try to chroot into it. Can't use pacman to fix because gnupg is broken. Try to pacstrap gnupg, but that can't overwrite files. Manually delete gnupg files one by one. Accidentally delete /bin.
@loshmi@aurocha Ooh, nasty! Wondering; would you consider #blendOS now, ie, in effect an #immutable Arch? Presumably, had that exact scenario arisen then, you'd simply lose that broken update, but still have the prior snapshot to continue working.
Having played with this in a VM i'm quite intrigued with it, but otoh my Host #ArchLinux continues to run sweetly so i have no desire to blow away a lovely system just to then get blendOS. Otoh, if i had to recover from a calamity like yours, i suspect i'd then be sorely tempted... 🤷♀️
@Ethon@johanneskastl@stdevel Ich verstehe die Motivation. Allerdings mit Flatpaks muss man dann zumeist auf IMHO sehr sinnvolle Integration zwischen den Anwendungen verzichten. Die sind dann soweit gekapselt, dass man beispielsweise eben nicht mehr von seinem Knowledge Management eine bestimmte E-Mail im Mailclient aufmachen kann.
Da setze ich lieber auf so Konzepte wie #NixOS, das man #immutable betreiben kann, wenn man (viel) Aufwand und Wissen reinsteckt.
FLOSS Weekly Episode 771: Kalpa — Because Nobody Knows what Hysteresis Is (hackaday.com)
This week, Jonathan Bennett and Dan Lynch talk with Shawn W Dunn about openSUSE Kalpa, the atomic version of openSUSE Tumbleweed, with a KDE twist. What exactly do we mean by an Atomic desktop? Is …