systemd - systemd

	Commit message (Collapse)	Author	Age	Files	Lines
*	Drop split-usr and unmerged-usr support	Luca Boccassi	2023-07-28	1	-2/+2
\| \| \| \| \| \| \| \| \| \|	As previously announced, execute order 66: https://lists.freedesktop.org/archives/systemd-devel/2022-September/048352.html The meson options split-usr, rootlibdir and rootprefix become no-ops that print a warning if they are set to anything other than the default values. We can remove them in a future release.
*	integritysetup: support mode=(journal\|bitmap\|direct)	Alfred Klomp	2023-06-08	1	-3/+16
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	Add a parameter to the integritytab file to set the mode in which to open the integrity volume. The mode can be journaled (the default), bitmap without a journal, or direct mode without a journal or a bitmap. This change removes the `no-journal' option because it is redundant, being replaced with `mode=direct'. Supercedes commit bcc1ee56c, from a week ago, which implemented `no-journal'. Resolves #27587
*	generators: change TimeoutSec=0 to TimeoutSec=infinity	Lennart Poettering	2023-06-06	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	With these settings we intend to turn off timeouts for possibly interactive/slow commands. The officially documented way to turn off the time-outs is to setting them to infinity. So far we set them to zero here though. This lead to some confusiong, for example #18224. Let's fix this by uniformly spelling out TimeoutSec=infinity. This doesn't change behaviour. It just makes our generated files match what we document, without relying on historic compat support. Fixes: #18224
*	Support no-journal for dm-integrity devices.	Russell Harmon	2023-05-30	1	-0/+3
\| \| \| \| \| \| \| \|	As documented in integritysetup.8, dm-integrity devices support running without a journal whatsoever. This change allows the CRYPT_ACTIVATE_NO_JOURNAL flag (the same as is used with `integritysetup --integrity-no-journal`) to be passed in during dmsetup by specifying the `no-journal` option in integritytab.5.
*	integritysetup: do not use crypt_init_data_device after crypt_init	Luca Boccassi	2022-08-04	1	-6/+6
\| \| \| \| \| \| \| \|	crypt_init_data_device() replaces the crypt_device struct with a new allocation, losing the old one, which we get from crypt_init(). Use crypt_set_data_device() instead. Enhance the test to cover this option too.
*	integritysetup: also validate volume name	Lennart Poettering	2022-03-31	1	-0/+6
\| \| \| \|	Exactly like for veritysetup/cryptsetup
*	integritysetup: also port to mangle_none()	Lennart Poettering	2022-03-31	1	-2/+2
\| \| \| \| \|	Let's make the tool work more like veritysetup/cryptsetup in this regard too.
*	integritysetup: log when attempted to detach already detached volume	Lennart Poettering	2022-03-31	1	-1/+3
\| \| \| \|	To make the tool behave more like cryptsetup/veritysetup
*	integritysetup: rename action → verb, to match other code	Lennart Poettering	2022-03-31	1	-5/+5
\|
*	tree-wide: unify some code that looks for --help in the command line	Lennart Poettering	2022-03-31	1	-5/+3
\|
*	integritysetup: Check args to prevent assert	Tony Asleson	2021-10-28	1	-7/+11
\| \| \| \| \| \| \|	The utility function parse_integrity_options is used to both validate integritytab options or validate and return values. In the case where we are validating only and we have specific value options we will assert.
*	Add stand-alone dm-integrity support	Tony Asleson	2021-10-15	4	-0/+463
	This adds support for dm integrity targets and an associated /etc/integritytab file which is required as the dm integrity device super block doesn't include all of the required metadata to bring up the device correctly. See integritytab man page for details.