Package: initrd-tools Version: 0.1.76 Severity: normal I use LVM2 on top of a dm-crypt device. With the initrd created by mkinitrd the cryptsetup command is called with wrong arguments. The -s 128 and -h plain options are missing. The system won't be bootable. If I hack mkinitrd to call cryptsetup with -c aes -s 128 -h plain then the system will boot without problems.
Here is my /etc/crypttab: crypt_vg1 /dev/ide/host0/bus0/target0/lun0/part3 none cipher=aes,size=128,hash=plain Maybe the information in /etc/crypttab should be used the same way as in the initscript to contruct the command line for cryptsetup. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-mm1 Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages initrd-tools depends on: ii coreutils [fileutils] 5.2.1-2 The GNU core utilities ii cpio 2.5-1.1 GNU cpio -- a program to manage ar ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM F ii dash 0.5.1-3 The Debian Almquist Shell ii fileutils 5.2.1-2 The GNU file management utilities ii util-linux 2.12p-2 Miscellaneous system utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
