I reassigned the ticket to pmount, since it relates to the way pmount-hal mounts the crypted volume (called by gnome-volume-manager), and not to something done by hal. Also, I changed it to a wishlist, since what I was asking for is not possible with the current way pmount-hal works.
I've a better view of the current behaviour, after having looked at the sources. AFAIU, the crypted volume won't be accessible until cryptsetup has been launched by pmount, so the label of the partition inside it is not accessible until it's mounted. Since the mount-point (potentially extracted from the label) will be determined before pmount-hal launches pmount, it's not possible to reach the label at that time. I think it may be possible to change pmount-hal (or pmount)'s behaviour in the following way, maybe : 1) first launch cryptsetup luksOpen on the device with the prompted passphrase 2) examine the label of the contained partition when it's successfully unocked (/lib/udev/vol_id /dev/mapper/_whatever_) 3) finaly mount on the corresponding mountpoint deduced of that label, or on the default mountpoint... Any comments welcome ;) -- Olivier BERGER <[EMAIL PROTECTED]> Ingénieur Recherche - Dept INF INT Evry (http://www.int-evry.fr) OpenPGP-Id: 1024D/6B829EEC
