[pkg-cryptsetup-devel] Bug#513149: ryptdisks_start with explicit volume does not give proper errors
Joachim Breitner
nomeata at debian.org
Mon Jan 26 21:14:23 UTC 2009
Package: cryptsetup
Version: 2:1.0.6-7
Severity: normal
File: /usr/sbin/cryptdisks_start
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
when trying to start a device with a crypttab entry using
cryptdisks_start directly, as in
$ cryptdisks_start media500
Starting crypto disk...done.
does not give an error message when the device is not present (in my
case, because I did not run vgchange -a y vg-500 yet).
While it is ok to ignore the entry during boot (it has the noauto flag),
it really should tell me about problems when I specifiy it explicitly.
Thanks,
Joachim
- -- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.27-1-amd64 (SMP w/2 CPU cores)
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.27-4 The Linux Kernel Device Mapper use
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libdevmapper1.02.1 2:1.02.27-4 The Linux Kernel Device Mapper use
ii libpopt0 1.14-4 lib for parsing cmdline parameters
ii libuuid1 1.41.3-1 universally unique id library
cryptsetup recommends no packages.
Versions of packages cryptsetup suggests:
pn dosfstools <none> (no description available)
ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs
ii udev 0.125-7 /dev/ and hotplug management daemo
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkl+J6gACgkQ9ijrk0dDIGyrIwCgwTAsDq5yGGLRqpBeaAoAhbrz
h6MAn2J5bJ05a1+f6FlAXdMe5H4htqTq
=WlNz
-----END PGP SIGNATURE-----
More information about the pkg-cryptsetup-devel
mailing list