570eae5007
Both sysext and confext used the host's /etc/initrd-release file even when --root=/somewhere was specified. A workaround was the SYSTEMD_IN_INITRD= env var but without knowing this it was quite confusing. Aside from users validating their extensions, the primary use case for this to matter is when the extensions are set up from the initrd where the initrd-release file is present when running but we want to prepare the extensions for the final system and thus should match for the right scope. Make systemd-sysext check for /etc/initrd-release inside the given --root= tree. An alternative would be to always ignore the initrd-release check when --root= is passed but this way it is more consistent. The image policy logic for EFI-loader-passed extensions won't take effect when --root= is used, though.
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