From 7ab064a6d60cf805765077b67d56c123f9cf3c58 Mon Sep 17 00:00:00 2001 From: Tom Gundersen Date: Sun, 18 Aug 2013 14:59:00 +0800 Subject: cryptsetup-generator: allow specifying options in /proc/cmdline MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The main usecase for this is to make it possible to use cryptsetup in the initrd without it having to include a host-specific /etc/crypttab. Tested-by: Thomas Bächler --- man/systemd-cryptsetup-generator.xml | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) (limited to 'man') diff --git a/man/systemd-cryptsetup-generator.xml b/man/systemd-cryptsetup-generator.xml index 215ac2d125..d6b7e49f13 100644 --- a/man/systemd-cryptsetup-generator.xml +++ b/man/systemd-cryptsetup-generator.xml @@ -137,6 +137,29 @@ will be activated in the initrd or the real root. + + + luks.options= + rd.luks.options= + + Takes a LUKS super + block UUID followed by an '=' and a string + of options separated by commas as argument. + This will override the options for the given + UUID. + If only a list of options, without an + UUID, is specified, they apply to any UUIDs not + specified elsewhere, and without an entry in + /etc/crypttab. + rd.luks.options= + is honored only by initial RAM disk + (initrd) while + luks.options= is + honored by both the main system and + the initrd. + + + luks.key= rd.luks.key= -- cgit v1.2.3-54-g00ecf