Sodele udev -v bestaetigt meine Vermutung, zumindest glaube ich das. Wie unten zu sehen ist mag er im Gegensatz zu einem truecrypt volume cryptsetup nicht wirklich. Kann mir jemand von einer funktionierenden Umgebung kurz pasten, wie sich udev bei cryptsetup-luks normalerweise verhaellt plus eventuelle Loesungsvorschlaege (da ich von udev noch nicht wirklich Ahnung habe)?
Mit Gruessen, rent
localhost ~ # cryptsetup luksOpen /dev/md4 dest
Enter LUKS passphrase:
UEVENT[1174702817.788550] add@/block/dm-1
udev_event_run: seq 1926 forked, pid [10595], 'add' 'block', 0 seconds old
udev_rules_get_name: rule applied, 'dm-1' is ignored
udev_device_event: device event will be ignored
udev_event_run: seq 1926 finished
udev_done: seq 1926, pid [10595] exit with 0, 0 seconds old
UEVENT[1174702817.796753] remove@/block/dm-1
udev_event_run: seq 1927 forked, pid [10596], 'remove' 'block', 0 seconds old
udev_db_get_device: no db file to read /dev/.udev/db/block@dm-1: No such file or directory
udev_rules_get_run: rule applied, 'dm-1' is ignored
udev_device_event: device event will be ignored
udev_event_run: seq 1927 finished
udev_done: seq 1927, pid [10596] exit with 0, 0 seconds old
localhost ~ # truecrypt /dev/hdd1 /mnt/hdd/
Enter password for '/dev/hdd1':
UEVENT[1174702870.520533] add@/block/dm-1
udev_event_run: seq 1928 forked, pid [10623], 'add' 'block', 0 seconds old
udev_rules_get_name: rule applied, 'dm-1' is ignored
udev_device_event: device event will be ignored
udev_event_run: seq 1928 finished
udev_done: seq 1928, pid [10623] exit with 0, 0 seconds old
UEVENT[1174702870.541699] mount@/block/dm-1
udev_event_run: seq 1929 forked, pid [10625], 'mount' 'block', 0 seconds old
udev_rules_get_run: rule applied, 'dm-1' is ignored
udev_device_event: device event will be ignored
udev_event_run: seq 1929 finished
udev_done: seq 1929, pid [10625] exit with 0, 0 seconds old
