2ff40c758e
The idea is to use this when building an image to mark the image as not needing updates after the reboot. In general it is impossible to say if any of the early boot update services can be safely skipped, except when the creator of the image knows all the contents there and has made sure that all the updates have been processed. (This is in fact what happens in a typical package-based installation: the packages have scriptlets which implement the changes during or after the installation process.) With this patch, the image build process can do 'systemd-update-done --root=…' at the appropriate point to avoid triggering of ldconfig.service, systemd-hwdb-update.service, etc. I didn't write --image=, because it doesn't seem immediately useful. The approach with --root is most useful when we're building the image "offline", which means that we have a directory we're working on.
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