We need to store state persistently for the software TPM (i.e. the root key). But given that TPMs are generally used to unlock the rootfs, this storage cannot be on the rootfs. Hence let's use the ESP instead, as the next best thing, that is guaranteed to exist during early boot, given we just were booted from it. This defines automatic logic for this, but does not cause the ESP mount job to be enqueued (since typically we don't actually want that mounted), this is left for the actual services that needs to be done. Note that the mount here is set up quite differently from the one from the host: since initrds are short-lived anyway, it seemed pointless to use autofs. Moreover this uses a fixed place to mount the ESP, inspired by the /sysroot/ + /sysusr/ mount naming. All that to simplify things a bit for the consumers (which is mostly swtpm)
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release
