00e3abe024
Let's order the fields from the most general to least: os name, os variant, os version, machine-parseable version details, metadata, special settings. I added section headers to roughly group the settings. The division is not strict, because for example CPE_NAME also includes the version, and PRETTY_NAME may too, but it still makes it easier to find the right name. Also split out Examples to separate paragraphs: almost all descriptions had "Example:" at the end, where multiple examples were listed. Splitting this out to separate paragraphs makes the whole thing much easier to read. Add missing markup and punctuation while at it. About - If not set, defaults to <literal>NAME=Linux</literal>. + If not set, a default of <literal>NAME=Linux</literal> may be used. and similar changes: in many circumstances, if this is not set, no value should be used. The fallback mostly make sense when we need to present something to the user. So let's reword this to not imply that the default is necessary. |
||
---|---|---|
.github | ||
.lgtm/cpp-queries | ||
.mkosi | ||
.semaphore | ||
catalog | ||
coccinelle | ||
docs | ||
factory/etc | ||
hwdb.d | ||
man | ||
mkosi.default.d | ||
modprobe.d | ||
network | ||
po | ||
presets | ||
rules.d | ||
shell-completion | ||
src | ||
sysctl.d | ||
sysusers.d | ||
test | ||
tmpfiles.d | ||
tools | ||
units | ||
xorg | ||
.clang-format | ||
.ctags | ||
.dir-locals.el | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.lgtm.yml | ||
.mailmap | ||
.packit.yml | ||
.vimrc | ||
.ycm_extra_conf.py | ||
configure | ||
LICENSE.GPL2 | ||
LICENSE.LGPL2.1 | ||
Makefile | ||
meson.build | ||
meson_options.txt | ||
mkosi.build | ||
NEWS | ||
README | ||
README.md | ||
TODO |
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.