Package: cryptsetup Version: 2:1.0.6~pre1+svn45-1 Severity: wishlist I just spent 2 hours figuring out why neither cryptdisks_start nor cryptsetup luksOpen would work but give a "Can not access device" error.
Turned out it was an already opened device :) It would be nice if the failure notice would tell so or at least hint at it. Another suggestion (not worth another bugreport): please add a newline after the message "<device> (stoppping)..." of cryptdisks_stop. Currently the next prompt starts right after the .... The same applies for cryptdisks_start. Thanks in advance -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cryptsetup depends on: ii dmsetup 2:1.02.24-3 The Linux Kernel Device Mapper use ii libc6 2.7-6 GNU C Library: Shared libraries ii libdevmapper1.02.1 2:1.02.24-3 The Linux Kernel Device Mapper use ii libpopt0 1.10-3 lib for parsing cmdline parameters ii libuuid1 1.40.6-1 universally unique id library cryptsetup recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
