OpenSuSE Man Pages

Man Page or Keyword Search:
Man Architecture
Apropos Keyword Search (all sections) Output format
home | help
x SuSE Linux 13.1-RELEASE x
x SuSE Linux 13.1-RELEASEx
SYSTEMD-CRYPTSETUP-GENERAsystemd-cryptsetup-genSYSTEMD-CRYPTSETUP-GENERATOR(8)

NAME
       systemd-cryptsetup-generator - Unit generator for /etc/crypttab

SYNOPSIS
       /usr/lib/systemd/system-generators/systemd-cryptsetup-generator

DESCRIPTION
       systemd-cryptsetup-generator is a generator that translates
       /etc/crypttab into native systemd units early at boot and when
       configuration of the system manager is reloaded. This will create
       systemd-cryptsetup@.service(8) units as necessary.

       systemd-cryptsetup-generator implements the generator specification[1].

KERNEL COMMAND LINE
       systemd-cryptsetup-generator understands the following kernel command
       line parameters:

       luks=, rd.luks=
           Takes a boolean argument. Defaults to "yes". If "no", disables the
           generator entirely.  rd.luks= is honored only by initial RAM disk
           (initrd) while luks= is honored by both the main system and the
           initrd.

       luks.crypttab=, rd.luks.crypttab=
           Takes a boolean argument. Defaults to "yes". If "no", causes the
           generator to ignore any devices configured in /etc/crypttab
           (luks.uuid= will still work however).  rd.luks.crypttab= is honored
           only by initial RAM disk (initrd) while luks.crypttab= is honored
           by both the main system and the initrd.

       luks.uuid=, rd.luks.uuid=
           Takes a LUKS superblock UUID as argument. This will activate the
           specified device as part of the boot process as if it was listed in
           /etc/fstab. This option may be specified more than once in order to
           set up multiple devices.  rd.luks.uuid= is honored only by initial
           RAM disk (initrd) while luks.uuid= is honored by both the main
           system and the initrd.

           If /etc/crypttab contains entries with the same UUID, then the
           options for this entry will be used.

           If /etc/crypttab exists, only those UUID specified on the kernel
           command line 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=
           Takes a password file as argument.

           For those entries specified with rd.luks.uuid= or luks.uuid=, the
           password file will be set to the password file specified by
           rd.luks.key= or luks.key

           rd.luks.key= is honored only by initial RAM disk (initrd) while
           luks.key= is honored by both the main system and the initrd.

SEE ALSO
       systemd(1), crypttab(5), systemd-cryptsetup@.service(8), cryptsetup(8),
       systemd-fstab-generator(8)

NOTES
        1. generator specification
           http://www.freedesktop.org/wiki/Software/systemd/Generators

systemd 210                                    SYSTEMD-CRYPTSETUP-GENERATOR(8)

Want to link to this manual page? Use this URL:
<
http://star2.abcm.com/cgi-bin/bsdi-man?query=systemd-cryptsetup-generator&sektion=8&manpath=>

home | help