Passing thoughts on Universal Blue and their ilk...

https://liam-on-linux.dreamwidth.org/97793.html

(Fairly rare tech blog post, from me. Repurposed Lobsters/HN comment, as often the case.)

Passing thoughts on Universal Blue and their ilk...

 It is very odd to me to watch OStree-based distros starting to take off and win recruits.<p>The only reason Red Hat needed to invent this very complex mechanism was because RH does not officially have a COW-snapshot capable filesystem in its enterprise distro.</p> <p>A filesystem with snapshot

Dreamwidth Studios
@lproven Ostree is not just a virtual FS with snapshotting capabilities. Ostree is image based and kind of declarative. This is not the case for SUSE's snapshotting concept, as far as I'm aware. This allows Ostree to do things that you can't do merely by rolling back snapshots:
@lproven Let's say the OS starts in a state called A1. We now install a package and end up in a new state A1'. Then we update the OS and end up in A2'. Because with Ostree installing packages works by layering, we can now remove that layer again and thus move directly from A2' to A2.
@lproven With SUSE's snapshots we either need to go from A2' back to A1 (if we haven't deleted it already) and then update to A2, or we uninstall the package using the package manager. But depending on the package manager installing and then uninstalling a package might not be guaranteed to lead to the same result as doing nothing. So by uninstalling the package we might actually create a new state A2'' != A2.
@lproven Furthermore with Ostree you can arbitrarely move between different images by using the rebase operation. As far as I'm aware you can even rebase from Silverblue to whatever ublue image and the other way around. Not sure if you can even move between atomic desktops and CoreOS though.
@lproven bootc takes this even a step further by using the standardized OCI image format for it's images.