On Sun, 2008-06-08 at 16:47 +0200, Jonas Meurer wrote:
> On 21/04/2008 Sam Morris wrote:
> > My solution is to add the following rules to udev's configuration:
> >
> > KERNEL!="dm-*", GOTO="device_mapper_end"
> > ACTION!="add|change", GOTO="device_mapper_end"
> > IMPORT{program}="/sbin/dmsetup export -j $major -m $minor"
> > LABEL="device_mapper_end"
> >
> > ENV{DM_NAME}=="temporary-cryptsetup-*", OPTIONS+="ignore_device"
> >
> > This tells udev to not send out a udev event if the device-mapper
> > mapping name starts with "temporary-cryptsetup-". HAL will therefore
> > never 'see' the temporary cryptsetup mapping that causes this problem.
> >
> > The final line of the above configuration should probably be added to
> > cryptsetup's configuration, since the "temporary-cryptsetup-*" mappings
> > are a cryptsetup-specific implementation detail. Alternatively, HAL
> > itself can be modified to ignore udev events where DM_NAME starts with
> > "temporary-cryptsetup-*".
>
> what's the current situation regarding this bug? should the cryptsetup
> package add a udev rules file containing the one line you suggested
> above?Well, it works for me--but I don't know whether the rule should be added by hal, cryptsetup, device-mapper or udev... at this stage in the release process I'm tempted to say, whichever one fixes it for lenny, and sort things out later. :) > > greetings, > jonas -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
signature.asc
Description: This is a digitally signed message part
