Daan De Meyer
505492d61c
Previously, all queued events were discarded on exit, hence several events might not be processed by udevd when it is restarted. Such situation especially easily happens on switching root. This makes queued events serialized on exit, and deserialized in the next invocation. Hence, no events should be lost during restarting udevd. This is important with the several aspects. Basically systemd-udev-trigger.service (re)triggers all devices anyway after switching root, But the service may be disabled or modified by admin. Moreover, the service produces only 'add' events, and thus the service cannot cover events with other actions generated by the kernel during switching root. Also, the userspace triggered events may not contain some parameters compared with events triggered by the kernel.
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