From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-px0-f178.google.com (mail-px0-f178.google.com [209.85.212.178]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 16 Jul 2010 14:05:42 +0200 (CEST) Received: by pxi5 with SMTP id 5so1382720pxi.37 for ; Fri, 16 Jul 2010 05:05:38 -0700 (PDT) Message-ID: <4C40499E.4020307@gmail.com> Date: Fri, 16 Jul 2010 19:59:26 +0800 From: Aaron Lewis MIME-Version: 1.0 References: <4C3FC795.6070007@gmail.com> <4C400D4F.6010100@redhat.com> <4C403A2A.5040004@gmail.com> <4C403BDA.8020405@archlinux.org> <4C403F3E.9030509@gmail.com> <4C4041E9.9040909@redhat.com> In-Reply-To: <4C4041E9.9040909@redhat.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Problem with udev and dmcrpyt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: dm-crypt@saout.de -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/16/2010 07:26 PM, Milan Broz wrote: > On 07/16/2010 01:15 PM, Aaron Lewis wrote: > >>> The "name" is whatever you call it when you run cryptsetup luksOpen (or >>> create). The file system inside the volume can be identified by UUID as >>> any file system can. >> >> For example ? With udev rules or dmcrypt configurations ? > > See ehat dm udev rules is doing - using DM_NAME attribute to create symlinks etc. > There is nothing special needed for dm-crypt - DM rules are common. > > ls /lib/udev/rules.d/*-dm-* > /lib/udev/rules.d/11-dm-lvm.rules > /lib/udev/rules.d/13-dm-disk.rules > /lib/udev/rules.d/95-dm-notify.rules Yep , so udev reads two directory as configurations ? + /etc/udev/rules.d + /lib/udev/rules.d All Right , i removed my hacks , now: %> sudo cryptsetup luksClose /dev/mapper/code %> sudo cryptsetup luksOpen /dev/sda8 code Kernel Messages: udevd-work[11168]: kernel-provided name 'dm-1' and NAME= 'mapper/temporary-cryptsetup-11166' disagree, please use SYMLINK+= or change the kernel to provide the proper name udevd-work[11168]: device node '/dev/mapper/temporary-cryptsetup-11166' already exists, link to '/dev/mapper/temporary-cryptsetup-11166' will not overwrite it udevd-work[11168]: kernel-provided name 'dm-1' and NAME= 'mapper/code' disagree, please use SYMLINK+= or change the kernel to provide the proper name udevd-work[11168]: device node '/dev/mapper/code' already exists, link to '/dev/mapper/code' will not overwrite it Doesn't looks like anybody else , wired problem. I should be able to get rid of those messages , right ? Many thanks. - -- Best Regards, Aaron Lewis - PGP: 0x4A6D32A0 FingerPrint EA63 26B2 6C52 72EA A4A5 EB6B BDFE 35B0 4A6D 32A0 irc: A4r0n on freenode -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxASZ4ACgkQvf41sEptMqCKhQCfbCvgWy3lAyMPwCmVMpCO5rRr c7oAnRzR4mMJI8FHkS5XUNKC72FeAarS =Ml7s -----END PGP SIGNATURE-----