Yu Watanabe
abb49d8e5a
`systemd-firstboot --image=` customizes an image by writing into its /etc. That doesn't work for images whose root file system is signed, which is exactly the kind of image you'd want to hand out and customize per deployment. Everything firstboot configures is also picked up as credentials at boot though, so the settings can just as well travel in a systemd-stub addon on the ESP, which isn't covered by the signature. This adds `--addon=NAME` for that. Instead of mounting the image, the settings are turned into the credentials of the same meaning (plus `system.machine_id` for the machine ID), packed into a cpio in the `.initrd` section of a addon, a kernel command line goes into `.cmdline`, and the result ends up as `loader/addons/NAME.addon.efi` in the ESP. The image is never mounted for that, the partition table is dissected to find the ESP and mtools does the writing. `--key=[NAME=]PATH` adds custom keys, say a certificate for verifying extension images, as `keyring.NAME` credentials. The name on the consuming side isn't settled yet, so treat that as a placeholder. The addon is unsigned, whether the stub picks it up is up to the Secure Boot policy, see #44362 for the stub side of this.
System and Service Manager
Details
Most documentation is available on systemd's website.
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