On Wed, 2006-09-13 at 22:05 +0200, Luca Berra wrote: > On Wed, Sep 13, 2006 at 12:36:38PM -0700, Piet Delaney wrote: > >On Wed, 2006-09-13 at 08:50 +0200, Luca Berra wrote: > >> On Tue, Sep 12, 2006 at 10:22:18PM -0700, Piet Delaney wrote: > >> > I just tried dm-crypt and there appears to have been a change in the > >> >/dev interface. > >> > >> please fix your udev rules and stop flooding lists with the same message > > > >How about explaining the apparently known problem with the udev rules; > >even Andrew Morton was unaware of the problem. I'll look and see if I > >can figure it out but given the testy nature of the environment I'd > >appreciate a few pointers. > > it is not a new problem > device mapper gets registered into sysfs as > /sys/class/misc/device-mapper, and it has been like this for ages My udev 50-udev.rules has: # create a symlink named after the device map name # note devmap_name comes with extras/multipath KERNEL="dm-[0-9]*", PROGRAM="/sbin/devmap_name %M %m", ... ... NAME="%k", SYMLINK="%c" device-mapper.1.02.09 has a hook in dmsetup that if it is invoked with the name devmap_name that it will create the link. Looks like it was only documented on the net; Ex: http://www.redhat.com/archives/dm-devel/2005-March/msg00079.html I would have had the device-mapper makefile put in the symbolic line from /sbin/devmap_name -> /sbin/dmsetup. > so if there is no udev rule, udev will create > /dev/device-mapper > > i just have: > KERNEL=="device-mapper", NAME="mapper/control" ok, sounds simple. I'll try it. Thanks. BTW, someone should consider adding the symbolic link in the makefile; might help others from tripping over this. -piet > > L. > -- Piet Delaney Phone: (408) 200-5256 Blue Lane Technologies Fax: (408) 200-5299 10450 Bubb Rd. Cupertino, Ca. 95014 Email: piet@xxxxxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part
