With the addition of /dev/disk/by-designator/ along with ID_DISSECT_PART_DESIGNATOR attr, it is now trivial to tell whether the swap device we hibernated into is the "auto" one. Hence use that bit of info and generate cryptsetup unit in hibernate-resume-generator if that's the case. Ideally, gpt-auto should really just handle swap already in initrd, which would save us a myriad of trouble and the system behaves more consistently. But I don't see that happening anytime soon. This is the second best option we have I reckon. Closes #27247 (#35328, #37330)
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
