All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] renaming of device
Date: Sat, 16 Jan 2010 17:22:30 +0100	[thread overview]
Message-ID: <20100116162230.GA21425@tansi.org> (raw)
In-Reply-To: <4B517B5E.2020203@redhat.com>

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 

  reply	other threads:[~2010-01-16 16:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 15:16 [dm-crypt] renaming of device Arno Wagner
2010-01-10 19:49 ` Arno Wagner
2010-01-10 20:33   ` Milan Broz
2010-01-11 16:17     ` Arno Wagner
2010-01-13  7:01     ` Luca Berra
2010-01-13 10:20       ` Sven Eschenberg
2010-01-13 13:13         ` Arno Wagner
2010-01-13 16:18           ` Sven Eschenberg
2010-01-13 17:29             ` Arno Wagner
2010-01-14 18:18               ` Sven Eschenberg
2010-01-14 21:42                 ` Arno Wagner
2010-01-14 22:16                   ` Sven Eschenberg
2010-01-14 22:46                     ` Arno Wagner
2010-01-15  2:17                       ` Sven Eschenberg
2010-01-15  3:58                         ` Arno Wagner
2010-01-15 11:28                           ` Sven Eschenberg
2010-01-16  0:30                           ` Ross Boylan
2010-01-16  2:46                             ` Arno Wagner
2010-01-16  8:39                               ` Milan Broz
2010-01-16 16:22                                 ` Arno Wagner [this message]
2010-01-16 18:52                                 ` Sven Eschenberg
2010-01-18 14:06                                   ` Milan Broz
2010-01-18 14:58                                     ` Sven Eschenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100116162230.GA21425@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.