9eb7f4cebf
Consider the following case: a user sets up a minimum rootfs for file system maintenance work in /run/nextroot/ dir directly. When they're done, they expect 'systemctl reboot' to perform a full reboot. But they keep soft-rebooting back to the tmpfs root, until they find out about $SYSTEMCTL_SKIP_AUTO_SOFT_REBOOT. So currently, when /run/nextroot/ is a normal dir, pid1 automatically turns it into a bind mount to soft-reboot into. This is good, but when combined with automatic soft-reboot it has an arguably unexpected behavior, since /run/nextroot/ can never go away in such a case. OTOH, if /run/nextroot/ is a mountpoint in the first place, the mount is *moved* so a second reboot would not trigger auto soft-reboot. Let's just make things more friendly to users, and do auto soft-reboot only if /run/nextroot/ is also a mountpoint.
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.