From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pv0-f178.google.com (mail-pv0-f178.google.com [74.125.83.178]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 16 Jul 2010 13:15:16 +0200 (CEST) Received: by pva18 with SMTP id 18so1162773pva.37 for ; Fri, 16 Jul 2010 04:15:15 -0700 (PDT) Message-ID: <4C403F3E.9030509@gmail.com> Date: Fri, 16 Jul 2010 19:15:10 +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> In-Reply-To: <4C403BDA.8020405@archlinux.org> Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable 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 On 07/16/2010 07:00 PM, Thomas B=E4chler wrote: > Am 16.07.2010 12:53, schrieb Aaron Lewis: >> device name is dynamiclly allocated , i think so. >> Shouldn't there be some ways to identify it like UUID ? In that case , >> i'll be able to put more accurate rules. >=20 > 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 ? >=20 >>>> How can i get rid of that together ? >> >>> Update package which provides DM new rules. Yor distro should provide >>> it if they update udev. >> >> Guess gentoo never provide such services. >=20 > They should. Upstream device mapper provides udev rules that should be > installed with device-mapper. If no udev rules are installed, I would > consider that a bug. >=20 --=20 Best Regards, Aaron Lewis - PGP: 0x4A6D32A0 FingerPrint EA63 26B2 6C52 72EA A4A5 EB6B BDFE 35B0 4A6D 32A0 irc: A4r0n on freenode