Lennart Poettering
9e7b691073
The man page is supposed to provide a "generalized, though minimal and modernized subset" (as per introductory pargapraghs), from a systemd perspective. But the thing is that /usr/include/ really doesn't matter to us. It's a development thing, and slightly weird (because it arguably would be better places in /usr/share/include/ or so). It's not going to be there on 95% of deployed systems, and we really don't want people to bother with it on such systems. We only define the skeleton of directories in this document, and it's expected that people extend it, and I think this really should be one of those dirs that is an extension of our skeleton, but not part of the skeleton, if that makes any sense.
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