LINUX Unplugged 656: Why KDE Linux Surprised Us
11 snips
Mar 2, 2026 They push KDE Linux hard, exploring its image-based, immutable design and how Plasma is packaged and updated. The team debates EROFS vs SquashFS, delta-update gaps, and system extensions for layering components. They test installer, encryption, and app delivery options like Flatpak and Nix. A self-hosted Nebula Commander control plane is demoed, with deployment, auth, and roadmap details.
AI Snips
Chapters
Transcript
Episode notes
KDE Linux Uses Immutable Images With Practical Tooling
- KDE Linux is an image-based, mostly immutable OS using Arch as a build base and EROFS for a sealed /usr to provide reproducible, secure system images.
- It leverages MKOSI to produce UKIs and systemd-sysupdate for A/B updates and rollbacks, prioritizing practical, existing tooling over reinventing the wheel.
Use systemd-sysupdate For Safe Image Updates
- Use systemd-sysupdate for atomic image swaps and rollback instead of trying to invent a new update mechanism.
- KDE Linux downloads a full new image, places it correctly, and updates bootloader entries so you can boot back if the update fails.
System Extensions Let You Layer Big Components
- System extensions (sysext) let KDE Linux layer large components like Plasma or frameworks on top of an immutable base without modifying the sealed root.
- Sysexts are heavyweight and still maturing, but they suit multi-file components better than single-binary user tools.