7352a0093f
We generally do _not_ want the same sysexts to be loaded in both initrd and exitrd phases. The environment is completely different and it's unlikely that the same code can be useful in both places. Nevertheless, it can be useful in _some_ cases, for example when the sysexts contains debugging tools. I think we don't need to differentiate between initrds and exitrds through SYSEXT_SCOPE, because the two types are made available in completely different locations and loaded through a different mechanism, with very little chance of an initrd being loaded as an exitrd without an explicit admin action (or the other way around). So let's not complicate our code or definitions by an explicit "exitrd" sysext designator, but just clarify that "initrd" also encompasses exitrds in this context.
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