summaryrefslogtreecommitdiffstats
path: root/man/directives-template.xml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* man: add "DNS resource record types" sectionZbigniew Jędrzejewski-Szmek2021-06-291-1/+7
|
* veritysetup-generator: add support for veritytabGaël PORTAY2021-01-151-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | This adds the support for veritytab. The veritytab file contains at most five fields, the first four are mandatory, the last one is optional: - The first field contains the name of the resulting verity volume; its block device is set up /dev/mapper/</filename>. - The second field contains a path to the underlying block data device, or a specification of a block device via UUID= followed by the UUID. - The third field contains a path to the underlying block hash device, or a specification of a block device via UUID= followed by the UUID. - The fourth field is the roothash in hexadecimal. - The fifth field, if present, is a comma-delimited list of options. The following options are recognized only: ignore-corruption, restart-on-corruption, panic-on-corruption, ignore-zero-blocks, check-at-most-once and root-hash-signature. The others options will be implemented later. Also, this adds support for the new kernel verity command line boolean option "veritytab" which enables the read for veritytab, and the new environment variable SYSTEMD_VERITYTAB which sets the path to the file veritytab to read.
* license: LGPL-2.1+ -> LGPL-2.1-or-laterYu Watanabe2020-11-091-1/+1
|
* man: drop obsolete HAVE_PYTHON conditionalZbigniew Jędrzejewski-Szmek2020-06-131-1/+1
| | | | | | It stopped making sense when automake support was dropped and python started being required to perform a build. Follow-up for 72cdb3e783174dcf9223a49f03e3b0e2ca95ddb8.
* man: document homed.confLennart Poettering2020-05-071-0/+9
|
* man: add specifiers section to directives indexZbigniew Jędrzejewski-Szmek2020-05-071-0/+8
| | | | | | The hack with getparent().txt is not very pretty, but the whole thing seems to work well enough. It is useful to figure out whihc specifiers are supported where.
* tools: move directive index template to separate fileZbigniew Jędrzejewski-Szmek2020-05-071-0/+182
In the beginning, it was rather short, and reasonable to include inline. Now it is long and unwieldy, let's split it out. While at it, let's reindent and wrap using our current standards.