Licensed to the public under https://creativecommons.org/licenses/by-sa/4.0/

about this event: https://c3voc.de

Licensed to the public under https://creativecommons.org/licenses/by-sa/4.0/

about this event: https://c3voc.de

Licensed to the public under https://creativecommons.org/licenses/by-sa/4.0/

about this event: https://c3voc.de

Licensed to the public under https://creativecommons.org/licenses/by-sa/4.0/

about this event: https://c3voc.de

Projekte: GlowPaka, Potato C4, Wanderalpakas, Sicher durch die Nacht, StatisTok, Servo-Gurt, Minecraft Shader, Wallet Finder, Safe Media, Anti-Stress Kuscheltier, Alpaka.Connect, Aquaponik

Licensed to the public under https://creativecommons.org/licenses/by-sa/4.0/

about this event: https://c3voc.de

Closing session of All Systems Go! 2025

Licensed to the public under https://creativecommons.org/licenses/by/4.0/de/

about this event: https://cfp.all-systems-go.io/all-systems-go-2025/talk/DR8ELH/

I overview how OS management is done at Meta. We run millions of Linux servers and we have to make sure that OS gets updated on all of them in a given period of time. To do that we developed several products: MetalOS (Image based version of CentOS), Antlir (image builder) and Rolling OS Update (a service that keeps a set of DNF repos in sync with upstream repos and uses them to update OS )

Licensed to the public under https://creativecommons.org/licenses/by/4.0/de/

about this event: https://cfp.all-systems-go.io/all-systems-go-2025/talk/VNCDRL/

The UAPI Boot Loader Specification defines conventions that let multiple operating systems and bootloaders share boot config files. So far, only systemd-boot implements it - and it’s UEFI-only by design.

As a result, hybrid UEFI/BIOS images require maintaining (and keeping in sync) two sets of bootloader configs: one for systemd-boot, and one for a legacy bootloader such as syslinux.

I set out to fix that by building a BIOS bootloader that uses the UAPI Boot Loader Specification - allowing both UEFI and legacy boot to use a single shared set of config files. This talk is about why that matters, how I built it, and what comes next.

In this talk, I’ll cover:

- What the UAPI boot spec is

- Why you'd want to use legacy boot instead of EFI/systemd-boot - *spoiler: you don't! but you might have to*

- How I implemented UAPI boot support for legacy BIOS

- What about UKIs?

- A live demo of the bootloader in action

- The current state of the project and what’s next

https://uapi-group.org/specifications/specs/boot_loader_specification

https://github.com/nkraetzschmar/bootloader

Licensed to the public under https://creativecommons.org/licenses/by/4.0/de/

about this event: https://cfp.all-systems-go.io/all-systems-go-2025/talk/ANC879/

Updates are a critical piece of managing your fleet of devices. Nowadays, Yocto-based distributions can utilize layers for well-established update mechanisms. But, did you know that recent releases of Yocto already come with a simple update mechanism?

Enter systemd-sysupdate: a mechanism capable of automatically discovering, downloading, and installing A/B-style updates. By combining it with tools like systemd-boot, we can turn it into a

comprehensive alternative for common scenarios.

In this talk, we will briefly introduce systemd-sysupdate, show how it can be integrated with your Yocto distribution, and share thoughts on how it can be improved further.

Licensed to the public under https://creativecommons.org/licenses/by/4.0/de/

about this event: https://cfp.all-systems-go.io/all-systems-go-2025/talk/MU7JM8/

`test.thing` is a VM runner which targets guests using an API defined by systemd. It started after a conversation at devconf about turning `mkosi qemu` into a library. A quick intro.

~~composefs is an approach to image-mode systems without the disk images. Files are stored in a de-duplicated content-addressed storage with integrity guaranteed through fs-verity. The last year has seen an acceleration of development on composefs-rs, a pure Rust implementation of the ideas behind composefs. Our goal is unification of the storage of bootable system images (via bootc), application Flatpaks, and traditional OCI container environments, bringing deduplication and integrity guarantees to all three. An overview.~~

Licensed to the public under https://creativecommons.org/licenses/by/4.0/de/

about this event: https://cfp.all-systems-go.io/all-systems-go-2025/talk/MLTTHW/