Return-Path: <wagner@tansi.org>
Received: from tansi.org (ns.km10532-04.keymachine.de [87.118.102.195])
	by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Sat, 16 Jan 2010 17:22:03 +0100 (CET)
Received: from gatewagner.dyndns.org (84-74-164-239.dclient.hispeed.ch
	[84.74.164.239]) by tansi.org (Postfix) with ESMTP id 7C5954250002
	for <dm-crypt@saout.de>; Sat, 16 Jan 2010 17:22:03 +0100 (CET)
Date: Sat, 16 Jan 2010 17:22:30 +0100
From: Arno Wagner <arno@wagner.name>
Message-ID: <20100116162230.GA21425@tansi.org>
References: <20100113172946.GA6329@tansi.org>
	<4B4F600A.7090107@whgl.uni-frankfurt.de>
	<20100114214257.GB23608@tansi.org>
	<4B4F97BD.3020909@whgl.uni-frankfurt.de>
	<20100114224627.GA24444@tansi.org>
	<4B4FD035.2030705@whgl.uni-frankfurt.de>
	<20100115035805.GA31381@tansi.org>
	<1263601811.26202.72.camel@corn.betterworld.us>
	<20100116024645.GA11543@tansi.org> <4B517B5E.2020203@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B517B5E.2020203@redhat.com>
Subject: Re: [dm-crypt] renaming of device
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On Sat, Jan 16, 2010 at 09:39:58AM +0100, Milan Broz wrote:
> On 01/16/2010 03:46 AM, Arno Wagner wrote:
> > It does. Each possible /dev/sd<x> has a defined, fixed 
> > major/minor, see Documentation/devices.txt in a Linux kernel 
> > source tree.
> 
> so long thread:-)
> 
> Well, the situation is more complicated.
> 
> If cryptsetup uses only "real" block devices (like /dev/sdaX),
> then fix to display proper device is is trivial.
> (Parsing is in cryptsetup internal, not system libdevmapper currently.)
> 
> But if you have stacked devices "virtual block devices"
> (crypt over MD or over LVM) it can be different - you want to see
> /dev/VG/LV as device, not /dev/dm-X.
> 
> (btw dm-X names are not persistent and were intended to be kernel internal
> only, unfortunately now are visible in userspace because of unified
> udev event processing. And renaming these nodes to me more user-frientdly
> in kernel is not easy because of various name length limits and different
> approach for renaming of active DM devices) 
> 
> But the real problem now is that device-mapper library is just
> in process of transition to udev (all nodes and symlinks will be created
> by udev and not internally in libdevmapper).
> And this changed (unified) some nodes to symlinks and vice versa.
> 
> With various maintainer's udev rules in various ditributions it creates nice
> mix and Debian usually modifies even default rules for dm devices.
> 
> (Actually if you have an udev rule, which creates another node and not
> symlink in /dev/scsi/..., it is  probably not correct, it should be symlink.)

I think so too, but I am unable to find it. Maybe I will just 
start to disable udev rules, until the behaviour goes away. 
Then I can file a bug report wth Debian.
 
> Anyway, I'll plan to fix it somehow in next minor release of cryptsetup
> (1.1.1 probably).

Looking forward to find out what your solutin will be ;-)

Arno




 
> Milan
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
> 

-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier