BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.all-systems-go.io//8AA87L
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-all-systems-go-2025-8AA87L@cfp.all-systems-go.io
DTSTART;TZID=CET:20250930T145000
DTEND;TZID=CET:20250930T151500
DESCRIPTION:systemd-sysext provides a nice way to enhance a distribution wi
 th a read-only root filesystem without the need to reboot. But there is ad
 ditional tooling necessary to manage the sysext images:\n* install an imag
 e which is compatible with the installed OS version\n* update installed im
 ages to the newest compatible version\n* rollback images in case of an OS 
 rollback\n* cleanup unneeded images\n\nIn this presentation I will talk ab
 out which tooling systemd itself provides for this (importctl\, updatectl\
 , ...) and what the benefits and disadvantages of this tools are compared 
 with real world use cases. In the end I created an own\, generic and distr
 ibution independent tool for this using systemd tools in the backend. Usin
 g openSUSE MicroOS as example I will demonstrate how we solved the problem
 s with it and how we integrated it in our update stack.
DTSTAMP:20260315T014413Z
LOCATION:Loft
SUMMARY:Integrating systemd-sysext images in an update stack - Thorsten Kuk
 uk
URL:https://cfp.all-systems-go.io/all-systems-go-2025/talk/8AA87L/
END:VEVENT
END:VCALENDAR