Zbigniew Jędrzejewski-Szmek
5134e18eed
Instead of defining the numbers only as fallback, always define our fallback number, and if we have the real __NR_foo define, assert that our number matches the real one. This will result in warnings when our fallback number is not defined, even if the kernel headers are new enough to define __NR_foo. This will probably annoy people compiling for seldom-used architectures, but hopefully it'll provide motivation to add the missing fallback defines. The upside is that we have a higher chance of catching the cases where we got the number wrong. Calling the wrong syscall is quite problematic, and with some back luck, it might take us a long time to notice that we got the number wrong on some rarely used architecture. Also, rework some of the fallback wrappers to not call the syscall with a negative number (that'd fail, but we'd got to the kernel and back). It seems nicer to let the compiler know that this can never succeed.
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 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.