[Pkg-cryptsetup-devel] Bug#467200: Bug#467200: Solution found, need input from cryptsetup, udev, hal, devmapper maintainers [was: Re: gnome-mount: Unable to mount encrypted volume]

[Jonas Meurer]

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?

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20080608/e2a3d967/attachment.pgp