
Chaos Computer Club - recent events feed
4,903 episodes — Page 57 of 99
Leveraging OpenStreetMap for hyperlocal geocoding of Twitter data: A spatiotemporal analysis of the 2016 Haifa (Israel) wildfire (sotm2025)
This study presents a geospatial framework that combines NLP, machine learning, and GIScience to extract and georeference tweets related to the November 2016 Haifa wildfire, enabling near real-time insights into urban fire dynamics. Using OpenStreetMap and GeoNames to geocode over 16,000 tweets, the researchers demonstrated strong spatial and temporal alignment with official fire incident reports, highlighting social media’s potential as a supplementary data source for disaster response. The approach offers a scalable model for leveraging crowdsourced and user-generated data in emergency informatics, especially in data-scarce regions. The increasing frequency and severity of urban wildfires demand new sources of near real-time information to support emergency response and disaster risk reduction [1-4]. In this study, we present an application for extracting and georeferencing the spatiotemporal distribution of tweets associated with the November 2016 wildfire in Haifa, Israel. The unprecedented urban fire influenced densely populated neighbourhoods, caused extensive infrastructural damage, and led to the evacuation of thousands of residents [5]. However, because of the nature and extent of the fire that lasted nearly 3 days, complete and reliable information concerning the emergence and development of new fire locations at the sub-city scale was only partial. Accordingly, management and decision-making procedures were complicated and some of the cascading events along the occurrence of the catastrophe were hard to be detected and addressed. The purpose of the study was to analyse tweets as a potential source of near real-time information and examine to what degree Twitter can be used to assist decision-making during occurrences on urban catastrophes. The implemented research combined Natural Language Processing (NLP), Machine Learning (ML), and Geographic Information Science (GIScience) to filter, classify, and precisely geolocate tweets at the city, neighbourhood or street-level resolution. One of the main components of the established geospatial framework was OpenStreetMap (OSM, https://www.openstreetmap.org, accessed July 2019), used in conjunction with the GeoNames gazetteer (http://www.geonames.org/, accessed July 2019) to construct a comprehensive spatial reference corpus. This enabled the geocoding of both explicitly and implicitly localized tweets that lack GPS metadata—an essential challenge given that only 1–3% of the tweets are geotagged with reliable geographic coordinates [6, 7]. We have collected approximately 2.4 million tweets using keywords related to the wildfire (in the Hebrew, Arabic, and English languages) between November 24th –27th, 2016. After classification using topic modelling and RCNN (Recurrent Convolutional Neural Networks) [8], around 114,000 tweets were labelled as relevant to the event. Of these, only 31 tweets were geotagged with geographic coordinates which is obviously an insufficient number of observations to perform spatial analysis. To overcome this shortcoming, we implemented a text-based georeferencing approach leveraging gazetteer data extracted from the OpenStreetMap and GeoNames databases. Accordingly, we converted 18 OSM shapefiles into a unified point dataset containing a wide variety of geographic features—ranging from neighbourhoods and roads to public buildings and natural landmarks. This dataset was merged with a version of the GeoNames corpus to create a point-based localized gazetteer representing the Haifa metropolitan area and its environs. For the purpose of geocoding, each point was associated with its place name in Hebrew, Arabic, or English. Following, the geocoding pipeline consisted of the following key steps: (1) NLP techniques including tokenization, stemming, and stop-word removal to extract named entities and spatial references from the tweet’s metadata [9]; (2) FuzzyWuzzy-based string matching algorithm that computes the Levenshtein distances between strings extracted from the tweet tokens and the place names in our gazetteer [10]; and (3) matchings were assigned a confidence score, which allowed us to filter or weight the credibility and accuracy of the spatial data. For example, georeferenced tweets with scores above 90% were deemed highly reliable for spatial trend detection. The process yielded 16,672 georeferenced tweets distributed across 130 unique localities within Haifa and its close vicinity. Following, we conducted a spatiotemporal inspection by aggregating tweets into 5×5 km grid cells and 8-hour intervals—bins that were informed by the density of localities extracted from the OSM/GeoNames hybrid gazetteer. We used Esri ArcGIS Pro to generate Kernel Density Estimation (KDE) maps [11] and 3D visualizations of the tweets’ distribution. The results presented strong temporal (Figure 1) and spatial (Figure 2) correspondence between georeferenced tweets and the officially reported fire incidents by the Israel Fire and Rescue Services (IF
Leveraging OpenStreetMap for hyperlocal geocoding of Twitter data: A spatiotemporal analysis of the 2016 Haifa (Israel) wildfire (sotm2025)
PlaceCrafter: Curating Urban Functional Regions through Platial Clustering of OpenStreetMap Points of Interest (sotm2025)
The world is not just made of streets, buildings, and zones; it is shaped by how people engage and interact with places in their everyday lives. This abstract presents a web-based geospatial tool that supports the mapping of these lived places and locales named PlaceCrafter. PlaceCrafter supports researchers in identifying platial regions: functional, human-centred areas that cross administrative and formal boundaries. The framework is built on OpenStreetMap, combining (near) real-time clustering, analysis, and statistical validation of these platial regions. PlaceCrafter supports researchers in exploring the subjective experiences of place through existing datasets and city structures. Contemporary urban analysis requires tools and analytical software that can not only capture the physical structure of the city, but also the dynamic and human-centred places that can emerge from everyday interactions. While these technologies, such as existing OpenStreetMap (OSM) [1] views and Geographic Information Systems (GIS) [2] are effective for spatial tasks, these abstractions fail to understand the notions of place when compared to space [3]. Recent work [4, 5] has sought to shift the focus towards platial information systems, tools which situate the human experience, subjective knowledge, and fuzzy representation as a comparison to existing spatial systems. These fuzzy, subjective, and personal representations attempt to model ‘place’ as a contrast to space, which may not align with traditional geometries or formal administrative zones. PlaceCrafter responds to this challenge by integrating a spatial-platial [6] approach to identifying regions that are functionally cohesive, representing dense and meaningful concentrations of specific points of interest (POI). The POIs are traditional representations of space within GIS [3], such as cafes, restaurants, museums, pathways, and places of worship. Rather than relying on the top-down designation of locations, PlaceCrafter supports users, analysts, and researchers curating clusters that represent how space is used as opposed to administratively divided. The approach aligns with recent calls in GIScience to shift from ‘space’ to ‘place’ in smart city analysis [7] and to continue building on work which has operationalised the sense of place in urban contexts [8]. PlaceCrafter is designed not just to analyse space, but to make its platial structure visible, explorable, and comprehensible to analysts, researchers, and planners. Figure 1 presents the web-based application, developed in TypeScript using React, Vite, Leaflet, Turf.js, and D3.js. The software uses the Overpass API [9] to retrieve (near, depending on number of POIs loaded) real-time user-filtered POI data. The datasets are organised into semantic categories based upon the existing OSM semantic structures [10]; these filters can be customised dependent on the analytical task. This functionality supports the broad purpose of the web-based application, which is to enable researchers and practitioners to understand city form and structure through a platial lens. PlaceCrafter is structured around four phases guided by the OSM filtering approach: the initial phase (1) focuses on filtering and selection of relevant OSM categories, building upon existing work, such as POI Pulse [11] which classifies regions using semantic signatures, and user behaviour to generate profiles of locations in the Los Angeles area and ClusterRadar [12] which supports comparative spatial clustering and parameter tuning through interactive visualisation to examine how clusters change temporally; the second phase (2) is where the fuzzy clustering approaches are applied interactively and include K-Means [13] for compact cluster formation, DBSCAN [14] for spatial structures, and hierarchical clustering for multi-level spatial structures. These clustering methods are applied to the filtered POI data to reveal platial regions. The penultimate phase (3) focuses on statistical validation, where each clustered region is evaluated using established spatial metrics. These evaluations include the nearest neighbour index to assess spatial clustering, silhouette scores [15] for understanding cluster coherence, and spatial autocorrelation is measured using a simplified Moran’s I statistic for insights into category-based dependency [16]; The final phase is (4) visualisation, which explores the concept of platial readability, where each region is presented not just spatially but semantically, with data supported by POI type, diversity score, and density metrics. Additionally, the platial visualisation techniques used support the emerging approaches to conveying ambiguity, overlap, and functional gradients [3, 17]. The visualisation subsystem is modular for a wide array of end-user requirements, supporting fuzzy spray can visualisation and region influence grids as presented in Figure 2, in addition to convex hulls, kernel density heatmaps, and region quality
Walking Milano: Unveiling the City’s Character Through 360° Street-Level Panorama Imagery. (sotm2025)
Walking Milano: Unveiling the City’s Character Through 360° Street-Level Panorama Imagery. (sotm2025)
Between September 2024 and August 2025, we conducted a comprehensive street-level survey of Milano, Italy, capturing approximately one million 360° panoramic images using a monopod-mounted camera setup. These images were uploaded to Mapillary, contributing to open-access urban geospatial data. This presentation shares practical insights into continuous data collection methods and analyzes urban characteristics discernible from the imagery, such as graffiti prevalence, urban greenery distribution, and the potential of these visuals as foundational data for 3D digital twin models. I will discuss the current capabilities and limitations of using crowdsourced street-level imagery for urban analysis and planning. Between September 2024 and August 2025, we undertook a comprehensive street-level survey of Milano, Italy, capturing approximately one million 360° panoramic images using a monopod-mounted camera setup. These images were uploaded to Mapillary, contributing to open-access urban geospatial data. This presentation shares practical insights into continuous data collection methods and analyzes urban characteristics discernible from the imagery, such as graffiti prevalence, urban greenery distribution, and the potential of these visuals as foundational data for 3D digital twin models. I will discuss the current capabilities and limitations of using crowdsourced street-level imagery for urban analysis and planning. Advancements in consumer-grade 360° cameras have significantly enhanced image resolution, with modern devices achieving up to 11K. These improvements, coupled with enhanced low-light performance, have expanded the temporal window for effective data collection beyond daylight hours. Mapillary’s object detection capabilities can identify over 150 object classes, including traffic signs, poles, and vegetation. However, challenges remain in detecting certain features like graffiti and nuanced vertical urban greenery, highlighting areas for future development. By analyzing the Milano dataset, we can assess the efficacy of current detection algorithms and identify gaps where manual annotation or algorithmic refinement is necessary. This analysis informs strategies for leveraging 360° imagery in urban planning, such as monitoring infrastructure conditions and informing greening initiatives. The session will conclude with a discussion on the future of crowdsourced 360° street-level imagery, exploring how community-driven data collection can support comprehensive urban analysis and planning efforts. Creative Commons Attribution 3.0 Unported https://creativecommons.org/licenses/by/3.0/ about this event: https://2025.stateofthemap.org/sessions/NRJEVM/
PlaceCrafter: Curating Urban Functional Regions through Platial Clustering of OpenStreetMap Points of Interest (sotm2025)
Awesome (OSM) Games (sotm2025)
OpenStreetMap and games feel like they go hand-in-hand and that's more than just coincidental. Both OSM and gaming have the power to bring people together, foster community engagement, and provide unique experiences. In fact, the OSM wiki has a page for games built using OSM data (https://wiki.openstreetmap.org/wiki/Games) and in recent years, we've seen the increase in the use of tools such as MapRoulette and StreetComplete that gamify the experience of contributing to OSM. While the latter is a very interesting topic in itself, this talk will focus on the former—games that use, but are not necessarily intended to contribute, OSM data. In this talk, we will explore the world of OSM-based/OSM-adjacent games to try and identify various game categories/genres and uses of OSM such as in location-based games (e.g. PokemonGO), serious and realistic simulation games, educational and trivia games, other niche/bespoke games, as well as both digital and tangible/tactile experiences. Furthermore, we will try to investigate the benefits and drawbacks of using OSM in games and look into other open source "games/game resources/gaming communities" (such as those in the Open Source Tabletop/RPG genre) to uncover possible intersections and opportunities. Whether you're a beginner or experienced OSM contributor, a game developer, or just a fellow gamer, this talk aims to spark new ideas and inspire further discussions, activities, and developments around the intersection of OpenStreetMap and games. Beyond the use of gamification for improving the OSM contributor experience, I feel that there is an opportunity to re-examine and revisit the broader topic of games using OSM data especially since OSM offers a rich and vibrant data source that can serve as the foundation for unique gaming experiences. How is/was OSM data used in games? What works/worked? What doesn't/didn't? Where (or where else) can OSM and games intersect? A lot of games use maps, can we use OSM there too? What other games can we create with OSM (e.g. Tactics? TTRPG? Board Games?). These are just some questions I'd like to ask and hopefully answer in the presentation. Creative Commons Attribution 3.0 Unported https://creativecommons.org/licenses/by/3.0/ about this event: https://2025.stateofthemap.org/sessions/LPDJXY/
Awesome (OSM) Games (sotm2025)
HOT 15-year Anniversary (sotm2025)
HOT 15-year Anniversary (sotm2025)
The Humanitarian OpenStreetMap Team (HOT) celebrates its 15th anniversary in 2025. This presentation will explore HOT's evolution from a small group of mappers responding to the Haiti earthquake to a global organization at the forefront of humanitarian mapping. We'll delve into key milestones, technological advancements, the growth of the HOT community, and the increasing role of local mappers in leading humanitarian responses. The talk will also address the challenges and opportunities for the next 15 years, including sustainability, technological innovation, and expanding the impact of open mapping in a changing world. This presentation will examine how HOT has transformed disaster response, development initiatives, and community empowerment through collaborative mapping. It will also look at how HOT has fostered a global community of mappers and the impact of open data on humanitarian efforts. Furthermore, the presentation will discuss the strategic directions HOT is taking to ensure its continued relevance and effectiveness in an ever-changing technological and global landscape, emphasizing the importance of partnerships, innovation, and inclusivity. Creative Commons Attribution 3.0 Unported https://creativecommons.org/licenses/by/3.0/ about this event: https://2025.stateofthemap.org/sessions/U9MSCX/
Opening (sotm2025)
Closing session of All Systems Go! 2025 (asg2025)
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/
Closing session of All Systems Go! 2025 (asg2025)
OS as a Service at Meta Platforms (asg2025)
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/
OS as a Service at Meta Platforms (asg2025)
One Boot Config to Rule Them All: Bringing UAPI Boot Specification to Legacy BIOS (asg2025)
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/
One Boot Config to Rule Them All: Bringing UAPI Boot Specification to Legacy BIOS (asg2025)
What's up with test.thing (asg2025)
`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/
Yocto's hidden gem: OTA and seamless updates with systemd-sysupdate (asg2025)
Yocto's hidden gem: OTA and seamless updates with systemd-sysupdate (asg2025)
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/
What's up with test.thing (asg2025)
A terminal for operating clouds: administering S3NS with image-based NixOS (asg2025)
S3NS is a trusted cloud operator that self-hosts Google Cloud infrastructure in France, targeting the SecNumCloud certification, the most stringent Cloud certification framework. SecNumCloud includes strict legal and operational constraints. To manage these systems securely and reproducibly, we’ve built a family of dedicated administration terminals based on the image based philosophy. These terminals rely on NixOS semantics and draw from the ParticleOS ecosystem: systemd-repart, and dm-verity, ensuring atomic updates, full immutability of the Nix store, and verifiable integrity of the boot chain and runtime system (measured boot), while using remote attestations by TPM2 when connecting to production assets. We will present the purpose of these terminals and what needs they serve along with their high level characteristics: partition layouts, provisioning and connection flow to the production assets. This talk will show an application of many of the concepts that were presented in the NixOS ecosystem and in All Systems Go itself by the systemd community. 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/TBDBDA/
A terminal for operating clouds: administering S3NS with image-based NixOS (asg2025)
UKI, composefs and remote attestation for Bootable Containers (asg2025)
UKI, composefs and remote attestation for Bootable Containers (asg2025)
With Bootable Containers (bootc), we can place the operating system files inside a standard OCI container. This lets users modify the content of the operating system using familiar container tools and the Containerfile pattern. They can then share those container images using container registries and sign them using cosign. Using composefs and fs-verity, we can link a UKI to a complete read only filesystem tree, guaranteeing that every system file is verified on load. We integrate this in bootc by creating a reliable way to turn container images into composefs filesystem trees, and then including the UKI in the container image. We will share the progress on the integration of UKI and composefs in bootc and how we are going to enable remote attestation for those systems using trustee, notably for Confidential Computing use cases. https://github.com/containers/composefs-rs https://github.com/bootc-dev/bootc https://github.com/confidential-containers/trustee 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/TNKPQS/
Leveraging bootable OCI images in Fedora CoreOS and RHEL CoreOS (asg2025)
Leveraging bootable OCI images in Fedora CoreOS and RHEL CoreOS (asg2025)
In last year's ASG!, bootc and bootable containers were introduced. In this talk, we'll go over what changed since last year, and how Fedora CoreOS and RHEL CoreOS are leveraging bootable containers to reduce maintenance and increase sharing. 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/87TFB7/
Introducing ue-rs, minimal and secure rewrite of update engine in Flatcar (asg2025)
Introducing ue-rs, minimal and secure rewrite of update engine in Flatcar (asg2025)
Introduce ue-rs, a fresh project that aims to be a drop-in reimplementation of update engine, written in Rust. The goal of ue-rs is to have a minimal, secure and robust implementation of update engine, required by A/B update mechanism of Flatcar Container Linux. Just like the existing update engine, it downloads OS update payloads from a Nebraska server, parses its Omaha protocol, verifies signatures, etc. This project, however, is different from the original update engine in the following aspects. First, it aims to be minimal, by reducing heavyweight legacies in the update engine. Moreover, written in Rust, it brings a huge advantage for security, especially memory safety, in contrast to the original update engine, which is written mainly in C++ and bash. Finally, in addition to traditional OS update payloads, it supports systemd-sysext OEM, which is supported by Flatcar. 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/JAC3DH/
container-snap: Atomic Updates from OCI Images using Podman’s Btrfs Driver (asg2025)
Dirlock: a new tool to manage encrypted filesystems (asg2025)
In the Linux world there are several tools and technologies to encrypt data on a hard drive, most falling into one of two categories: block device encryption (like LUKS) or stacked filesystem encryption (like EncFs or gocryptfs). This presentation will introduce Dirlock, a new tool that belongs to a third category: native filesystem encryption, using the kernel's fscrypt API. Dirlock is currently being developed and its aim is to provide a flexible way to encrypt files, suitable for both user accounts and arbitrary directories, with full PAM integration, support for hardware-backed mechanisms such as FIDO2 or TPM and with a D-Bus API for easy management. 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/AAWNQT/
container-snap: Atomic Updates from OCI Images using Podman’s Btrfs Driver (asg2025)
Traditional package updates using tools like RPM or Zypper can introduce risks, such as incomplete updates or accidentally breaking the running system. To overcome these challenges, we developed **container-snap**, a prototype plugin designed to deliver atomic OS updates—updates that are fully applied or rolled back without compromising the system's state. container-snap leverages OCI images as the source for updates and integrates seamlessly with openSUSE’s [tukit](https://github.com/openSUSE/transactional-update) to enable transactional OS updates. By utilizing Podman’s btrfs storage driver, it creates btrfs subvolumes directly from OCI images, allowing systems to boot from the OCI image. This approach empowers users to construct their own OS images using familiar container image-building tools, like Docker or [Buildah](https://buildah.io/). In this session, we’ll dive into: - The architecture and technical implementation of container-snap - Challenges encountered during development and how we resolved them - Key lessons learned along the way - A live demo showcasing container-snap in action Come and join this session to learn more about how to boot from an OCI image without bricking your system! 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/YTCMSG/
pidfd: What have we been up to? (asg2025)
File descriptors for processes on Linux have been available for quite some time now. Userspace has adapted them widely. Over the last two years or so we've extended the abilities of pidfds significantly. This talk will go over all the new features and deep dive into their implementation and usage. 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/3BMJVH/
pidfd: What have we been up to? (asg2025)
Forget zbus, zlink is the future of IPC in Rust (asg2025)
Last year, Lennart Poettering of the systemd fame, [gave a presentation](https://media.ccc.de/v/all-systems-go-2024-276-varlink-now-) at this very same conference, where he introduced Varlink, a modern yet simple IPC mechanism. He presented a case for Varlink, rather than [D-Bus](https://en.wikipedia.org/wiki/D-Bus) to be the future of Inter-process communication on Linux. As someone who works on D-Bus, I took upon myself to prove him wrong, only to find out that I achieved exactly the opposite. It didn't take long before I got convinced of his vision. Since I was largely responsible for giving the world [an easy to use D-Bus Rust library](https://crates.io/crates/zbus), I thought it's only fitting that I do the same for Varlink. This talk will be the story of the creation of such a library, the challenges I faced, where Varlink fits the Rust idioms really well and where it does not and how all of this affected the development and the API. 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/SYGBNH/
Forget zbus, zlink is the future of IPC in Rust (asg2025)
CentOS Proposed Updates: Bridging the Gap between development and production (asg2025)
CentOS Stream is especially suited for production deployments. In these environments it's often common to develop improvements to distribution packages and want to contribute them upstream. Unfortunately, until very recently that required one to then maintain their own build and deployment pipeline for the packages, at least until the changes made their way into the distribution. CentOS Proposed Updates (CPU) SIG aims to bridge this gap - changes that have been submitted as merge requests can be built in this SIG, providing those who run Stream in production with access to needed updates while they make their way into CentOS Stream. We hope this will help increase collaboration between RHEL engineers, CentOS Stream contributors, and the rebuild community as well, especially those that have distributions derived from CentOS Stream directly (such as AlmaLinux with AlmaLinux OS Kitten), as everyone can focus on making improvements without reinventing their own build pipelines. 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/9QUZNY/
Privilege delegation for rootless containers, what choices do we have? (asg2025)
CentOS Proposed Updates: Bridging the Gap between development and production (asg2025)
Privilege delegation for rootless containers, what choices do we have? (asg2025)
Going for minimal containers with restricted system calls and unprivileged users is the usual Kubernetes approach these days, and it works great for most web apps. However, the development of more complex infrastructure extensions frequently hinders application functionality. While looking for a solution to deploy virtiofsd in an unprivileged container for KubeVirt, we stumbled on seccomp notifiers. Seccomp notifiers are a kernel feature which monitors syscalls and get notifications to a userspace application when a syscall is executed. Alternative options involved either the use of a custom protocol using UNIX sockets or the deployment of virtiofs as a privileged component alongside the unprivileged VM. After our evaluation, the seccomp notifier turned out to be the simplest solution among all the choices. Unfortunately, the main constraint is the monitor's resilience after a restart, such as after a crash or an upgrade. This limitation forced us to back up to one of the less elegant approaches. But there is hope how this could be solved! The session will explain why seccomp notifiers are a lean solution to avoid extra userspace communication and synchronization, the current limitations and possible future solutions to overcome today’s challenges. Our experience will teach audiences several methods for dividing their privileged infrastructure. Utilizing virtiofsd as an actual example and a target application for KubeVirt integration and deployment. We will discuss the difficulties of using rootless containers in this session, as well as the design patterns, technologies, and tactics we thought about and ultimately chose to maintain or reject. 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/SPGAXS/
New Linux Kernel Coredump Infrastructure (asg2025)
Coredumping on Linux has long been a nightmare. Currently two modes are supported: (1) Dumping directly into a file somewhere on the filesystem. (2) Dumping into a pipe connected to a usermode helper process spawned as a child of the system_unbound_wq or kthreadd. For simplicity I'm mostly ignoring (1). There's probably still some users of (1) out there but processing coredumps in this way can be considered adventurous especially in the face of set*id binaries. The most common option should be (2) by now. It works by allowing userspace to put a string into /proc/sys/kernel/core_pattern like: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h The "|" at the beginning indicates to the kernel that a pipe must be used. The path following the pipe indicator is a path to a binary that will be spawned as a usermode helper process. Any additional parameters pass information about the task that is generating the coredump to the binary that processes the coredump. In the example core_pattern shown above systemd-coredump is spawned as a usermode helper. There's various conceptual consequences of this (non-exhaustive list): - systemd-coredump is spawned with file descriptor number 0 (stdin) connected to the read-end of the pipe. All other file descriptors are closed. That specifically includes 1 (stdout) and 2 (stderr). This has already caused bugs because userspace assumed that this cannot happen (Whether or not this is a sane assumption is irrelevant.). - systemd-coredump will be spawned as a child of system_unbound_wq. So it is not a child of any userspace process and specifically not a child of PID 1. It cannot be waited upon and is in a weird hybrid upcall which are difficult for userspace to control correctly. - systemd-coredump is spawned with full kernel privileges. This necessitates all kinds of weird privilege dropping excercises in userspace to make this safe. - A new usermode helper has to be spawned for each crashing process. On recent kernels a new mode has been added making use of AF_UNIX sockets. This talk will talk about the new modes, how they can be used, what advantages they have in comparison to the other modes, and look at technical implementation details. 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/MADB7R/
New Linux Kernel Coredump Infrastructure (asg2025)
Modernizing GNOME (asg2025)
GNOME has collected some very old code over the years. During the recent GNOME 49 release, we've made some drastic cleanups. Most visibly, we've dropped support for X11 and gained many dependencies on systemd. Let's explore some of the what and why for these changes! 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/FQE7QZ/
Modernizing GNOME (asg2025)
Slim device software with systemd targets and nspawn (asg2025)
It has been 10 years since Axis Communications had a presentation at the systemd conference. Back then, we have shown how we have increased our product quality, stability and boot times by porting our platform to systemd. 10 years later, we had different challenges to keep the resource usages and boot times under control. We have started from bottom up and sliced our software for this purpose. This work also got us inspired to create virtual versions of our hardware products that we cluster deploy using systemd's nspawn. We have hundreds of engineers working on a software platform that is the base for different product types. It is a different challenge to keep the resource usages of different software composition when so many independent engineers collaborate together. We have applied a different strategy to keep our products as slim and as optimized as possible using different systemd principles like targets, slices, resource prioritization. As a side effect of this work, we have started from ground up and started to virtualize our products using systemd-nspawn. The next step for us was to figure out how in best way to cluster deploy our virtual products so that we can increase the quality of our end to end systems. 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/Z3NGWJ/
Slim device software with systemd targets and nspawn (asg2025)
GNOME OS' prêt-à-booter image (asg2025)
GNOME OS is a distribution based around systemd-sysupdate. This year, we finally created a live installer image using the same /usr partition as the installed OS. The main innovation however is the ability to install without the need to reboot. The user can start working while the installation is happening. This live image is built using systemd-repart. And the installer itself also uses systemd-repart. But systemd-repart is not the complete solution and we had to solve some challenges. 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/QRJVL3/