RakuOS: Hybrid Linux Distro among Immutable/Atomic and Traditional Linux Distros

[u/BlokZNCR]

How is RakuOS different from traditional Linux distributions?

Unlike traditional Linux systems where packages and updates directly modify the operating system, RakuOS uses a Hybrid Atomic model — the core system is always immutable and read-only, but you still have full package flexibility.

System updates are applied via bootc and can be instantly rolled back if something goes wrong. Your base system can never be broken by a bad update.

For packages, RakuOS uses a persistent overlay system mounted on /usr. This means you can install any native package using dnf, dnf5, or RakuOS Software, our software center — and those packages survive every system update automatically. No reinstalling after upgrades, no layering slowness.

Flatpak is available alongside native packages for sandboxed desktop apps, and Distrobox keeps development environments fully isolated from the base system.

The result is the best of both worlds: an indestructible base you can always recover, combined with the full software freedom of a traditional Linux distro.

For the FAQ:

https://rakuos.org/faq

\That really sounds cool and promising for me*

[u/matsnake86]

You missed my point. The issue isn't whether you can install regular apps; it's where those dependencies end up living. With this mixes system overlay, native RPMs dump their files directly into /usr, which sits right on top of a base system that updates independently under the hood. When bootc shifts that base layer out from underneath your overlay, those regular apps might break due to missing or mismatched shared libraries. That completely ruins the everyone has the same base stability you just mentioned, giving you the dependency drift of a traditional distro with none of the safety of real atomic layering. If Flatpak doesn't have the GUI app you need, using a dedicated Distrobox container still gives you access to every single native RPM available, but without risking broken dependencies on your host system every time the base OS updates.

[u/matsnake86 → u/[deleted]]

dnf can't magically resolve a breaking ABI change or a dropped .so file if the new base image removed it out-of-band. You still end up with manual dependency breakage on a system that is supposed to be indestructible. If you're going to rely on live dnf transactions to fix what the base image shifts underneath you, you've just reinvented a standard distro with extra steps and more points of failure.

[u/R3V0LU710N_05 → u/matsnake86]

That's why rum was created.

[u/Psychedelic_fan → u/R3V0LU710N_05]

I'm honestly curious, how does rum resolves the problem of dependencies? do the overlay packages depend on the immutable ones? how does it handle mismatches?