This teachs the LUKS backend UID mapping, similar to the existing logic for the "directory", "subvolume" and "fscrypt" backends: the files will be owned by "nobody" on the fs itself, but will be mapped to logging in user via uidmapped mounts. This way LUKS home dirs become truly portable: no local UID info will leak onto the images anymore, and the need to recursively chown them on activation goes away. This means activation is always as performant as it should be.
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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
