bafe34ddbe
The package notes are nice standard mechanism to figure out the exact name and version of a program or a library stored in a file, without running the code. In the beginning this was designed for the purpose of analyzing core dumps, but we've since started to use it more generically to identify files. The same need to identify PE/COFF files occurs, for example for systemd-boot and other files intended for UEFI. It has also been requested by people working on bootupd (https://github.com/coreos/bootupd). The text is changed to say "Executable" or "ELF or PE/COFF" wherever "ELF" was used previously. The description for PE/COFF files is very brief. AFAIK, we don't have the same "note" mechanism there [1], so just a normal section is used. The alignment rules for PE/UEFI are different and change over time, so no specific alignment is specified. Other requirements for the PE/COFF section are based on what ukify currently does for the .osrel section: 5 .osrel 00000056 000000010132f000 000000010132f000 0002b600 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA The name ".pkgnote" is used as suggested by Daan De Meyer. This corresponds to the ".note.package" name used for ELF. ".package" was also suggested, but I think that is too generic and carries more risk of a conflict with a different use. [1] https://learn.microsoft.com/en-us/windows/win32/debug/pe-format Also zero/0 is replaced by NUL to clarify that a single 0 byte is meant.
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