Systemd, the Unix init system, will support the Rust programming language for new modules, developer Christian Brauner announced. Brauner said the feature had been merged as version 263 was under construction, allowing Rust code for new leaf components but not porting existing C code or writing Rust for components that other components depend on.
The feature follows the splitting of a previous pull request into five parts, with part two containing the Rust support. The second PR says Rust is only used for new leaf components, adding that existing C code is not ported and nothing that other components depend on is written in Rust. Rust code will be built with Meson instead of Cargo, the Rust language's usual build system, and must not use the standard library, a common practice for embedded Rust programming. The project requires Rust version 1.85 or later, bindgen version 0.71.1 or newer, and Meson 1.4.0. Brauner noted in a separate post that the team would have liked to support Rust in systemd core, but Rust's support for dynamic libraries is not yet sufficient.
The previous release, version 262, appeared about a month ago. Writing systemd modules in Rust is distinct from calling systemd from Rust code, which has been possible through tools such as the systemd crate since 2015.
Analysis
Why This Matters
- Allows Rust developers to contribute directly to systemd modules, potentially expanding the contributor base.
- Marks a cautious step toward integrating Rust into a critical Linux component, balancing innovation with stability.
- The restriction to new leaf components limits risk but also limits Rust's safety benefits to non-core areas.
Background
Systemd is the system and service manager for most Linux distributions, handling startup and process management. It has traditionally been written in C. This announcement represents the first official support for Rust within the systemd project itself.
What to Watch
- Whether future systemd releases expand Rust usage as Rust's dynamic library support matures.
- Community reaction, particularly from existing C developers and downstream distributions.
- The implementation of part one of the change, which includes helpers for enrolling certificates into kernel keyrings.
Checked
11 claims in this story checked against 1 source: 11 supported.
Show each claim
- SupportedSystemd will support Rust modules, as developer Christian Brauner announced.www.theregister.com - Articles: “That means that systemd 263 is now under construction, and developer Christian Brauner announced on Mastodon that his new feature has been merged.”
- SupportedNew leaf components can be written in Rust, subject to restrictions.www.theregister.com - Articles: “Rust is only used for new leaf components. Existing C code isn't ported and nothing that other components depend on is written in Rust.”
- SupportedBrauner announced the feature had been merged while systemd 263 was under construction.www.theregister.com - Articles: “That means that systemd 263 is now under construction, and developer Christian Brauner announced on Mastodon that his new feature has been merged.”
- SupportedExisting C code will not be ported, and components that other components depend on will not be written in Rust.www.theregister.com - Articles: “Existing C code isn't ported and nothing that other components depend on is written in Rust.”
- SupportedThe previous pull request was split into five parts, with part two containing Rust support.www.theregister.com - Articles: “The previous effort, which was pull request #44144, has now been split into five separate parts. Part 2, support programs written in Rust, is the banner item.”
- SupportedRust code will be built with Meson rather than Cargo.www.theregister.com - Articles: ““No cargo. Everything is built with meson.””
- SupportedRust code must not use the standard library, a practice described as normal for embedded Rust programming.www.theregister.com - Articles: “The third stipulation is that any Rust code must not use the standard library. For those more familiar with C, this may sound extreme, but it's normal for embedded Rust programming.”
- SupportedThe project requires Rust 1.85 or later, bindgen 0.71.1 or newer, and Meson 1.4.0.www.theregister.com - Articles: “It needs Rust version 1.85 or later. ... It also calls for bindgen version 0.71.1 ... or newer, and Meson 1.4.0”
- SupportedIn a separate post, Brauner said the team would have liked Rust support in systemd core, but Rust's dynamic-library support is not yet sufficient.www.theregister.com - Articles: “Brauner added an interesting little coda in a second Masto post: saying that the team would have liked to support Rust in the core of systemd, but currently, Rust’s support for dynamic libraries isn't quite there yet.”
- SupportedThe previous release, version 262, appeared about a month ago.www.theregister.com - Articles: “Agent P and his trusty team released systemd version 262 about a month ago.”
- SupportedWriting systemd modules in Rust is distinct from calling systemd from Rust code, which tools such as the systemd crate have enabled since 2015.www.theregister.com - Articles: “It's perhaps worth noting that writing systemd modules in Rust isn't the same thing at all as calling systemd from Rust code. There are several tools for doing that, and they have been around for years: for example, the systemd crate first appeared in 2015.”
