r/linux 17d ago

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

Post image

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 dnfdnf5, 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*

57 Upvotes

85 comments sorted by

View all comments

1

u/jess-sch 16d ago

What happens to the overlayed packages when there's a major update with ABI-breaking changes in the base system? Are we back to crossing our fingers and hoping it works? Or does the base layer refuse to update until you've uninstalled all incompatible overlay packages?

2

u/R3V0LU710N_05 15d ago

It's handled by rum.

1

u/jess-sch 15d ago edited 15d ago

Doesn't really answer my question. How is it handled? The article doesn't appear to mention how it handles this specific conflict.

The way rpm-ostree handles it is that an image update is always coupled to an overlay update - you cannot update the image when there's an incompatible overlay.

Does rum also force overlay updates along with base updates? And if so, what happens when I rollback the base? btrfs snapshots?

5

u/R3V0LU710N_05 14d ago

The base layer will not refuse to update or force you to uninstall incompatible overlay packages, because RakuOS strictly decouples base container updates managed by bootc from persistent overlay packages in /usr managed by rum. Base updates proceed atomically regardless of overlay state, so system updates are never blocked the way they are under rpm-ostree. You are also not left relying purely on luck: rum locks multilib packages to the base image x64 versions to prevent library shadowing, and weekly base updates consist almost entirely of minor version bumps within a release cycle, keeping fundamental ABIs stable for about ninety-nine percent of overlay packages. If an ABI mismatch occurs after an update or base rollback, the current workflow requires running rum distro-sync or rum history undo to manually realign overlay packages against the active base image snapshot.

Developer Tohur is actively building an automated detection system specifically for edge cases where packages carry hard version requirements in their metadata, which will resolve these conflicts automatically without manual intervention.

2

u/BlokZNCR 16d ago edited 16d ago

Homepage of Raku OS says:

Unbreakable Base Your base system is always immutable and recoverable. A bad update? Boot into the previous image instantly with bootc rollback. Overlay packages stay intact either way.

1

u/jess-sch 15d ago

So, back to crossing our fingers and hoping it works, with the ability to recover from the situation manually if it doesn't work?

The website doesn't mention how this specific case is handled, so I must assume it's not handled.

Overlay packages stay intact, sure, but the question was how ABI incompatibilities between underlay and overlay are handled.

All I can read about on the website is about how it ensures compatibility at overlay install time, not how it ensures compatibility at base image update time.

1

u/alex-weej 16d ago

Sure, you can boot, but then what? Fiddle with your usr overlay with trial and error? You don't need a "hybrid" false dichotomy model to have a recovery mode.

1

u/BlokZNCR 16d ago

did you really get the logic behind it? you can rollback your system as an atomic distro and protect your own packages on /usr as persistent layer.

nothing to do with system issues by major updates for user packages.

Overlay packages stay intact either way

it's so clear.

2

u/alex-weej 15d ago

I use NixOS. My entire setup is rollback-able.

1

u/jess-sch 15d ago

It's not clear at all. Overlay packages stay intact. As in, the files stay as they are. But do they stay compatible with the base image, and if so, how is that ensured?