This primarily introduces a context object for each operation, so that we later can instantiate one for each varlink op we execute, and can safely lifecycle all operation parameters for each subequent call. This also reworks the root dir handling to be fd based. This drops explicit CHASE_TRIGGER_AUTOFS from a bunch of chase() calls that operate within the ESP/XBOOTLDR, while it keeps them in place for the chase() calls that find the top-level ESP/XBOOTLDR inode. This reflects the fact that we explicitly support autofs for the ESP/XBOOTLDR itself, but below it expect no further mounts, just plain VFAT. This changes behaviour of the interaction of $KERNEL_INSTALL_CONF_ROOT and --root=: the former will now be taken relative to the host root, and will no longer be affected by --root=. This follows similar behaviour in kernel-install, where it is very explicitly documented in the man page (the bootclt man page does not document this). This is strictly speaking a compat breakage, but i think a very minor, niche one, and I think the pain afflicted by this change is probably neglible compare to the unsystematic behaviour comapred to kernel-install.
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
