1a25a77f3e
The logic of running_in_chroot() has been the same since the introduction of this function in b4f10a5e8956d26f0bc6b9aef12846b57caee08b: if /proc is not mounted, the function returns -ENOENT and all callers treat this as false. But that might be the most common case of chrooted calls, esp. in all the naïve chroots that were done with the chroot binary without additional setup. (In particular rpm executes all scriptlets in a chroot without bothering to set up /proc or /sys, and we have codepaths in sysusers and tmpfiles to support running in such an environment.) This change effectively shortcircuits various calls to udevadm, downgrades logging in tmpfiles, and disables all verbs marked with VERB_ONLINE_ONLY in systemctl. detect-virt -r is also affected: $ sudo chroot /var/lib/machines/rawhide before> systemd-detect-virt -r && echo OK Failed to check for chroot() environment: No such file or directory after> systemd-detect-virt -r && echo OK OK
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.