From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GKKLsTzdglYA for ; Sat, 3 Aug 2013 22:48:02 +0200 (CEST) Received: from mail-ea0-x234.google.com (mail-ea0-x234.google.com [IPv6:2a00:1450:4013:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sat, 3 Aug 2013 22:48:01 +0200 (CEST) Received: by mail-ea0-f180.google.com with SMTP id h10so919543eaj.25 for ; Sat, 03 Aug 2013 13:48:00 -0700 (PDT) Received: from [192.168.2.24] (56.157.broadband5.iol.cz. [88.100.157.56]) by mx.google.com with ESMTPSA id n5sm21723117eed.9.2013.08.03.13.47.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 03 Aug 2013 13:47:59 -0700 (PDT) Message-ID: <51FD6C5D.7070501@gmail.com> Date: Sat, 03 Aug 2013 22:47:25 +0200 From: Milan Broz MIME-Version: 1.0 References: <51FD17F0.5090805@gmail.com> <20130803175733.GA7976@tansi.org> In-Reply-To: <20130803175733.GA7976@tansi.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Cryptsetup FAQ montly pointer 8/13 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de 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