On 5/16/22 12:10, Chris Murphy wrote: > On Fri, May 13, 2022 at 3:20 PM przemek klosowski via devel > > >> Unfortunately, I believe that the current upgrade workflow requires a >> root disk three times the total installed package size: each package is >> there as the original version, the RPM of the upgrade in the cache >> directory, and as a new image before the old one is purged. > > Yeah I'm not sure it's currently possible to do an atomic update with > dnf or rpm, hence rpm-ostree. Or txnupd and btrfs snapshots > (essentially dnf and rpm keep doing what they're doing, but create a > snapshot of the running system, and update the snapshot out of band, > rather than stomping on the currently running OS). Exactly. This is one of the big value propositions of RPM-OSTree. Silverblue (desktop), Fedora CoreOS (Server), or Fedora IoT (Edge/IoT) are options here. If your "update" runs out of space for whatever reason then the upgrade is stopped and you won't be in a half upgraded state. As Chris mentioned there are also things like BTRFS snapshots or LVM snapshots, etc. that can help you go back in time. Dusty _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
