Futureweb

Open Source

systemd merged a path for new leaf programs in Rust. The core library is not that path, and the keyring helper is not in the merge.

systemd merged Rust support for new leaf programs. No Cargo, Meson builds them, and libsystemd is still C. The keyring helper is not merged.

The short version

Pull request 44324 merges support for writing new leaf programs in Rust. The project's constraints, stated on the earlier request it replaced, are no Cargo, Meson, C linkage, and no standard library beyond core and alloc. libsystemd stays C. Phoronix says the first program, systemd-keyring-setup, is not in this merge. A test program's size is Phoronix's measurement, not a release note.

The merge is for new leaves

Phoronix reported on October 24, 2026 that systemd had merged support for writing programs in Rust. The merge it points at is pull request 44324. An earlier request, 43551, was the design note and was closed in favor of 44324. The constraints written on that earlier request are the ones this page will use, because they are the project's own limits: Rust for new leaf components, not a port of the existing C, no standard library, no crates beyond core and alloc, Meson as the build, and C linkage only. Christian Brauner's comments, as Phoronix relays them, say the Rust binaries should behave like the C binaries and that Cargo is not part of the build.the Board election is a different openSUSE fact.

libsystemd is outside the merge

The same account says the core library is not moving. Phoronix reports that a Rust dynamic library is the blocker for libsystemd, which is a separate problem from compiling a leaf binary. A reader who hears systemd merged Rust and concludes that the library users link against is now a Rust crate has read a headline past the pull request. The leaf programs are new code. The C that already ships stays where it is.memory safety in a release note is a different claim.

The keyring helper is not the merge

Phoronix says the first real program, systemd-keyring-setup, is expected and is not part of what just merged. Until that program lands, the merge is build support and a test program. This page will not describe the helper's behavior, because the helper is not the merged code. A future commit can be a future brief. October 24's document is the pull request that landed. Asked directly, Did systemd rewrite libsystemd in Rust? No. The merged work is for new leaf programs. The project has said the shared library is still blocked. This page does not describe that block as a bug report.Open Responses is a specification, not a systemd unit.

Size is one test, and it is the article's

Phoronix says a test program came out around 32KB where a C version was around 20KB, and it relays Brauner's view that the difference is marginal and that the binaries do not depend on Cargo. Those numbers are the article's report of a test build. They are not a table in a systemd release announcement. This page does not remeasure the binary. It also does not treat a test program as the size of systemd as a whole. The flag Phoronix mentions, rust set to auto, is a build option in that account, not a switch this page tells anyone to flip.KeePassXC's stable release is a different project.

What 263 means here

Phoronix says the work will be part of systemd 263. That is a version the article assigns to the upcoming release, not a tag this page verified on a tarball. If 263 ships without the keyring helper, both facts can be true: the leaf support merged, and the first tool did not. The pull request is the fact of record for the merge. The version is the article's placement of it.

Two pull requests, one of them closed

Request 43551 is the closed discussion of the rules. Request 44324 is the one Phoronix says merged. Quoting a constraint from the closed request is fair only because the project carried those constraints forward as the design. This page does not paste build files, crate lists, or a sample main. The constraint that matters to a reader is the shape: new leaves, Meson, no Cargo, C linkage, and a library that stays in C.

Who this is for

The people in scope are systemd's own developers adding a new small program, and distributions that package systemd and will eventually see a rust build option. Users who start services with the tools they already have are not asked to do anything by this merge. A distribution that disables the option still has the C tree. Phoronix is the outside account. The two pull requests are the project's documents. A Norwegian reprint of Phoronix would not be a third investigation, and this page does not use one.the Linux 7.4 short slice is a different patch.

What the page will not claim

It will not say systemd is now a Rust project. It will not say the keyring helper shipped. It will not turn a 12KB gap on a test program into a general tax. It will not print a meson line for a reader to paste. The impact is a new place in the tree where a future leaf can be Rust, under rules the project wrote down before the merge. Asked directly, Is systemd-keyring-setup in the merge? Phoronix says it is the first program expected, and that it is not merged yet. The October 24 story is the build support, not that helper shipping.

The date

Phoronix's story is October 24, 2026. The merge it describes may have landed on the previous review. The news date is when the outside account appeared. The pull request is the record of what merged. Between them, the keyring helper remains unmerged in that account, and libsystemd remains C. The short answer this page will stand on is this: Pull request 44324 merges support for writing new leaf programs in Rust. The project's constraints, stated on the earlier request it replaced, are no Cargo, Meson, C linkage, and no standard library beyond core and alloc. libsystemd stays C. Phoronix says the first program, systemd-keyring-setup, is not in this merge. A test program's size is Phoronix's measurement, not a release note.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. systemd pull request 44324
  2. systemd pull request 43551
  3. Phoronix

Questions

Did systemd rewrite libsystemd in Rust?

No. The merged work is for new leaf programs. The project has said the shared library is still blocked. This page does not describe that block as a bug report.

Is systemd-keyring-setup in the merge?

Phoronix says it is the first program expected, and that it is not merged yet. The October 24 story is the build support, not that helper shipping.

Does the systemd Rust work use Cargo?

The constraints on the request this merge replaced say no. Builds go through Meson. Binaries are supposed to behave like the C ones.

What does Phoronix's 32 kilobyte figure measure?

Phoronix describes a test program at about 32KB against about 20KB for a C counterpart. That is one comparison in the article, not a size for every future tool.

Which systemd release is this aimed at?

Phoronix says the work is headed for systemd 263. The pull request is the merge. A version number in a news article is not a tarball this page downloaded.