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 hIn3OoIWXE4O for ; Sun, 4 Aug 2013 01:01:22 +0200 (CEST) Received: from awesome.dsw2k3.info (unknown [IPv6:2a01:198:661:1f::3]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sun, 4 Aug 2013 01:01:22 +0200 (CEST) Received: from localhost (localhost.localdomain [127.0.0.1]) by awesome.dsw2k3.info (Postfix) with ESMTP id E4B26C0D05 for ; Sun, 4 Aug 2013 00:50:28 +0200 (CEST) Received: from awesome.dsw2k3.info ([127.0.0.1]) by localhost (awesome.dsw2k3.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V7JX7T+44PTM for ; Sun, 4 Aug 2013 00:50:27 +0200 (CEST) Received: from citd.de (p5B15A1AF.dip0.t-ipconnect.de [91.21.161.175]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by awesome.dsw2k3.info (Postfix) with ESMTPSA for ; Sun, 4 Aug 2013 00:50:27 +0200 (CEST) Date: Sun, 4 Aug 2013 00:51:20 +0200 From: Matthias Schniedermeyer Message-ID: <20130803225120.GA26923@citd.de> References: <51FD17F0.5090805@gmail.com> <20130803175733.GA7976@tansi.org> <51FD6C5D.7070501@gmail.com> <20130803214715.GB9684@tansi.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130803214715.GB9684@tansi.org> 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 03.08.2013 23:47, Arno Wagner wrote: > On Sat, Aug 03, 2013 at 10:47:25PM +0200, Milan Broz wrote: > > 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. > > I thought so too, but the only thing I have in my /dev/disk/by-id > are my raid devices, nothing else, and I do have normal partitions. There must be something wrong(tm). E.g. just looking for the SSD my operating system is placed on i get 3 different entries: (Ignoring the partitions) lrwxrwxrwx 1 root root 9 Jul 28 03:17 ata-Samsung_SSD_840_PRO_Series_S12RNEACC37670P -> ../../sda lrwxrwxrwx 1 root root 9 Jul 28 03:17 scsi-SATA_Samsung_SSD_840S12RNEACC37670P -> ../../sda lrwxrwxrwx 1 root root 9 Jul 28 03:17 wwn-0x5002538550114fa0 -> ../../sda Counting all symlinks i have 31 in by-id! This is also a Debian System with a custom kernel (3.10.3). udev itself has a README somewhere describing what CONFIG parameters have to be set for udev to fully work. I look through that some ages ago and i had a few missing back then. Also "compatiblity with old userspace"-options like: CONFIG_SYSFS_DEPRECATED should be disabled. -- Matthias