From: "Thomas Bächler" <thomas@archlinux.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] /etc/crypttab not needed?
Date: Fri, 20 Jan 2012 16:38:44 +0100 [thread overview]
Message-ID: <4F198A84.6090406@archlinux.org> (raw)
In-Reply-To: <20120120161820.f999420c.public1@divara.de>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
Am 20.01.2012 16:18, schrieb Markus Melms:
> Hi,
>
> what is the advantage of using /etc/crypttab?
>
> When I was using it, I got errors during shutdown: "stopping early
> crypto disks failed". This sounds sensible since the root-fs is
> encrypted.
>
> Now that I'm not using it, disks still get mounted on startup and the
> error during shutdown is gone.
>
> Is it ok to not use /etc/crypttab? I'd rather not use it, makes it
> easier for me to synchronise /etc between different clients.
crypttab is not a part or feature of cryptsetup. Ask the Debian people
about it.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
prev parent reply other threads:[~2012-01-20 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 15:18 [dm-crypt] /etc/crypttab not needed? Markus Melms
2012-01-20 15:34 ` Yves-Alexis Perez
2012-01-28 9:39 ` Markus Melms
2012-01-20 15:38 ` Thomas Bächler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F198A84.6090406@archlinux.org \
--to=thomas@archlinux.org \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox