(without having read the article) after-update filesystem rollback sounds like what Suse has offered for about 10 years: https://www.suse.com/c/introduction-sys

(without having read the article) after-update filesystem rollback sounds like what Suse has offered for about 10 years: https://www.suse.com/c/introduction-system-rollbacks-btrfs-and-snapper-sles-11-sp2/ https://www.suse.com/c/introduction-system-rollbacks-btrfs-a... There just hasn't been much demand for it. There are a bunch of other mechanisms used instead, like redundant systems and gradual rollouts, working with full system images (or container images) instead, etc. For personal-ish systems, things are reliable enough, and if there is a problem you can't just stop updating, you'll need to fix it soon anyway. I've been updating a debian install on my home fileserver for 3 major debian releases, 5+ years ...