Kai Lueke
2e4c2f8df7
When the mutable directory didn't exist but gets created with --mutable=yes then it used to get mode 700 and later it got patched by a chmod because it is the top layer and must match the target hierarchy. This meant one could not call the function to resolve the mutable directory twice before the mount because it has a check for a proper mode when the directory exists which is the case for the second call. Also, this resulted in /var/lib/extensions.mutable getting created with mode 700 which is not really required. Don't rely on the chmod for the upper dir but directly create the directory with the right mode by first creating all missing directories with 755 as a sane default and then changing the mode as needed for the mutable directory.
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