This is just an anecdote, but I run Fedora Silverblue on my work laptop, and
I've toyed with distri in VMs. Even though I have had more exposure to
Silverblue and have had to solve more problems in Silverblue (including
packaging Flatpaks and becoming proficient with toolbox.), I would say I
understand distri more.
A big part of this complexity comes from the fact that Silverblue is using
OSTree to make the base installation immutable. Flatpaks also use OSTree to do
application versioning, but in a less general way than distri. In practice, a
lot of “applications” (which would be packages in distri) are not handled
through Flatpak (and OSTree) but through toolbox, which is basically a
container with a mutable file system and the existing RPM packaging
As a user, I’m more interested in the direction that distri is going, but the
systems built on OSTree are undeniably cool and make sense for many
Hope that helps.
On Wed, May 20, 2020, at 10:47, Michael Stapelberg wrote:
thanks for your interest!
I have only read about ostree and have never used it myself, so take
what I write with a grain of salt :)
OSTree or libostree is a project that combines a “git-like” model for
committing and downloading bootable filesystem trees, together with a layer
to deploy them and manage the bootloader configuration. OSTree is used by
rpm-ostree, a hybrid package/image based system that Silverblue uses. It
atomically replicates a base OS and allows the user to “layer” the
traditional RPM on top of the base OS if needed.
Based on this (and on the confirmation in
changing the ostree layer requires a reboot), I think ostree is more
focused on reproducible immutable scenarios. This is a great model for
production infrastructure, e.g. as a container host.
distri’s immutability is limited to the individual package level.
I.e., while you can not change what e.g. /ro/vim-amd64-8.2-5/
contains, you can install different versions of vim without a reboot.
distri resembles a traditional Linux distribution more in that regard,
with the twist that packages are immutable, multiple versions are
co-installable, and installation/updating is extremely fast.
In general, distri focuses on the package manager and packaging
infrastructure aspects, not on the OS aspect. We don’t currently have
a story for /etc, any special bootloader integration, and so on.
Does that help put things into perspective?
Have you tried distri yet? Check out
https://distr1.org/getting-started/ if you have a few minutes. Playing
around with the system might be good to get a feel for it :)
On Wed, May 20, 2020 at 10:52 AM Sergio Tortosa Benedito
Hello, I've been kind of following for a time and like it quite a bit, I
also know about OSTree and I wanted to know how these two compare, since I
know that distri implements things like multiple versioning, that distri
also has (though ostree allows for multiple os versions), but ostree also
has other features, concretely atomic upgrades, which is what i like the
most in there. And could be OSTree and distri mixed, if that makes sense?
--Best regards, Sergio