Comparison of Linux Software Update Technologies
summary
Compares specific open‑source update systems and their tradeoffs: classic deb/rpm non-atomic package updates risk partial failures; dual‑partition dual A/B full-image schemes use U-Boot bootcount and watchdogs to atomically switch images and rollback; incremental atomic systems like OSTree and swupd store rootfs as git-like object stores and apply binary deltas (smaller transfers) but require immutable-root assumptions and reboots or complex live switching. Mentions projects and tooling: Software Update (C), Mender (Go, client+server, systemd/uboot assumptions, Siemens users), OSTree/swupd adopters (GNOME continuous, Clear Linux, AGL).
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:58Overview
- 2:00History
- 3:34Modern Packaging
- 5:36Requirements
- 8:48Traditional Method
- 12:21Incremental Atomic Updates
- 14:21Container Updates
- 15:42Software Update
- 20:03Software Description
- 28:43Reference Platform
- 29:51OStree
- 39:44SWPD
- 42:54Containerbased solutions
- 44:37Free talks
- 47:07Authentication
- 50:37Recovery
related talks
43mOTA Updates in the Wild: Lessons from the Field
34mComparing Linux OS Image Update Models
51mUsing SWUpdate to Upgrade Your System
44mUpdating an Embedded System with SWUpdate Framework
39mHow to Choose a Software Update Mechanism for Embedded Linux Devices
11mImmutable Linux systems and how they work
47mOrchestrated Android-Style System Upgrades for Embedded Linux
42mEvolution of (OTA) Update in the IoT World