81 days ago · 6 min read1114 words · Tech · hide · Fediverse post

This article is about two desirable traits in system upgrades: atomicity and being able to roll back. Atomicity: the upgrade is either applied in full or not applied at all. The system is not left in a broken state because, e.g., “the package manager updated half of the files and then died”. This includes situations like a power failure mid-upgrade. Rollback-capable: if a system upgrade fails, or doesn’t work, it’s still possible to use the device in a previous system state. These two traits dramatically increase the reliability of a device that’s updated in the field, where the risk of an unusable device after an upgrade should be as minimal as possible. A common anti-pattern: immutable images[permalink] A common trend nowadays is to entangle these two features with immutable system images: the whole OS ships as an image, the entire image is downloaded (or perhaps a delta, layers, etc.) rather than overwriting individual files, ensuring atomicity. The old image is retained,…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town