Lennart Poettering
814db2ae79
Let's make sure each container run by unpriv users is known by both instances. Making it known by the host instance ensures it is resovlable by nss-myhostname (and various other tools), but making it known by the per-user instance means the user can fully manage it on their own. This simplifies the code a bit too, i.e. we always allocate a scope ourselves now, and just register it, instead of letting machined do that under some circumstances. THere's little value in that and it simplifies things for us quite a bit.
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