From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 16 Jul 2010 13:26:37 +0200 (CEST) Message-ID: <4C4041E9.9040909@redhat.com> Date: Fri, 16 Jul 2010 13:26:33 +0200 From: Milan Broz 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> In-Reply-To: <4C403F3E.9030509@gmail.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: , To: Aaron Lewis Cc: dm-crypt@saout.de 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 (on my Gentoo test system) No need to hack udev rules yourself and reinvent the wheel. Milan