From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Cryptsetup FAQ montly pointer 8/13
Date: Sat, 03 Aug 2013 22:47:25 +0200 [thread overview]
Message-ID: <51FD6C5D.7070501@gmail.com> (raw)
In-Reply-To: <20130803175733.GA7976@tansi.org>
On 3.8.2013 19:57, Arno Wagner wrote:
>> For plain crypt (or Truecrypt) you have no UUID, so you cannot use it.
>> (You can use uuid/wwid of underlying device as mentioned above
>> but this is not be present always.)
>
> Indeed. I tried both when I wrote the entry, only to find that
> neither worked on my system (Debain with custom kernel).
>
> As this is not a distrioution specific FAQ (there are those)
> distribution specific stuff shopuld not go into it. Of course
> documentation for a specific distribution can contain specific
> advice that is not general, and some people have already asked
> me about such things, also with regard to encrypted swap.
Device UUID/model etc should not be distribution specific,
udev /dev/disk/by-id* is quite standard among distibutions here.
In fact, udev reads it directly from /sys attributes, as the same
as lsblk does.
Maybe FAQ should also note that kernel device names (sda/sdb etc) is
NOT generaly persistent between reboots. (Usually it is the same but
nothing guarantees it, e.g. plugged USB disk or new SATA card can change
ordering and names). This is important mainly if you use swap keyword
whis is formatted on boot.
Milan
next prev parent reply other threads:[~2013-08-03 20:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 14:10 [dm-crypt] Cryptsetup FAQ montly pointer 8/13 Dragan Milivojević
2013-08-03 14:47 ` Milan Broz
2013-08-03 17:57 ` Arno Wagner
2013-08-03 20:47 ` Milan Broz [this message]
2013-08-03 21:47 ` Arno Wagner
2013-08-03 22:51 ` Matthias Schniedermeyer
2013-08-03 17:47 ` Arno Wagner
2013-08-03 12:49 ` Alex Elsayed
-- strict thread matches above, loose matches on Subject: below --
2013-08-02 21:54 Arno Wagner
2013-08-03 13:51 ` Robert Nichols
2013-08-03 17:46 ` Arno Wagner
2013-08-04 15:02 ` Sven Eschenberg
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=51FD6C5D.7070501@gmail.com \
--to=gmazyland@gmail.com \
--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