Kai Lüke
0eee5712fd
Up to now there was no clear ordering of confext and sysext units. Normally, configuration should be able to influence the behavior of services (config files or unit drop-ins), so it makes sense to order confext before sysext. The mounting from the initrd for the final system makes this less important together with the fact that live merges/ refreshes can encode unit restarts now. Yet I think it's better to know what gets merged first and if wanted one can avoid encoding restarts if one doesn't care about later live content changes. Where it matters more for me is consistent behavior for the refresh check during boot for non-verity images because they get compared by file handle and mount ID which means whether the overlay was set up or not determines the identity and decides if we do a refresh or not and this should not vary by boot merely due to timing or other dependencies impacting the ordering. (Note that one extension type shipping another extension type is not the reason for the ordering and these cycles should be avoided because they never free the mounts and backing loop devices.) (cherry picked from commit 7197b862b2a132ea044fed59d914d5eb3e8ae9dd)
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