One Config to Rule Them All: From systemd to Reliable Embedded Upgrades
summary
Argues for a concrete, versioned layering: /usr defaults (vendor-provided), /etc overrides (fragments/conf.d) and /run ephemeral, using tools like systemd, systemd-confext, conf.d patterns, overlayfs and AB-style partitions to enable validation, measurements and rollback for fleet upgrades. Describes Viata-style single-file config that generates /etc at boot (Perl implementation), supports schema validation and rollbacks, and shows this model can enable read-only rootfs deployments, factory reset, partial adoption and compliance with rules like the EU CRA.
AI-written summary · about
chapters (6)
- 0:00Introduction and motivation
- 3:54Current configuration problems
- 11:22Prior art and limitations
- 16:03Vyatta-style configuration approach
- 21:43System-wide requirements for upgrades
- 26:13Call to action and future vision
related talks
41mWill it Boot? -- The Case for Platform Standards in Embedded
50mThe ultimate guide to software updates on embedded Linux devices
41mCase Study: Switching from Asymmetric to Symmetric Software Updates
49mGeneric System for Safe Rootfs/Kernel Upgrades without Single-Point of Failure
33mUsing Open Source Software to Build an Industrial-grade Embedded Linux Platform...
49mUntangle spaghetti of the bare metal images and modes
35mDevOps Days MTL 2019- Yannick Brosseau
24mPython Untethered: Building Robust Embedded Systems
