BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2026//talk//GWM39L
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-devconf-cz-2026-GWM39L@pretalx.devconf.info
DTSTART;TZID=CET:20260619T140000
DTEND;TZID=CET:20260619T143500
DESCRIPTION:systemd-sysext is a standard mechanism for overlaying `/usr` on
  any systemd-based OS. The spec and tooling exists\, but what happens when
  you push it past "hello world" into production software - GPU drivers\, K
 ubernetes\, container runtimes?\n\nFlatcar Container Linux has been shippi
 ng all of these as sysext images since 2022. Docker and containerd don't e
 xist as binaries in the base OS - they're sysext images. Kubernetes can up
 grade independently of the OS via sysext + sysupdate.\n\nThis talk covers 
 what broke\, what we fixed\, and what we contributed upstream to systemd. 
 You'll see the two hardest engineering problems - dynamic linking collisio
 ns and library path isolation - and the open source tools (Flix and Flatwr
 ap) that solve them. We'll discuss when sysext is the right tool and when 
 rpm-ostree is better. \n\nWhether you work on FCOS\, Flatcar\, or any othe
 r systemd-based distro\, sysext is already in your systemd. This talk tell
 s you what to expect when you use it for real.
DTSTAMP:20260430T125059Z
LOCATION:E112 (capacity 156)
SUMMARY:systemd-sysext in Production: What We Learned Extending /usr Withou
 t a Package Manager - Brian Exelbierd
URL:https://pretalx.devconf.info/devconf-cz-2026/talk/GWM39L/
END:VEVENT
END:VCALENDAR