When we don't know the sector size of the actual block device, because we're building an image in a loopback file and no sector size was specified explicitly, let's use 4096 as the sector size for filesystems, verity and LUKS. This should be the most compatible option, since 4096 will also work on devices with sector size 512 or 2048. For the actual GPT partition table size, we stick with 512 as the default value since UEFI firmware and the kernel will only try to read the GPT partition table from the first LBA on the device and the sector size for most devices is still 512. It can also be trivially modified when copying the image to another device using --copy-from + --sector-size.
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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
