Package: cryptsetup
Version: 2:1.4.3-4
Severity: important

Dear Debian folks,


following the instructions in `README.initramfs.gz` to encrypt a root
partition and running `update-initramfs -u` the file `/etc/crypttab` is
not included in `initrd.img*` and therefore one has to manually open the
device in the BusyBox(?) shell. In that shell I verified that
`/etc/crypttab` does not exist.

Do the instructions need an update or is this a bug in
`update-initramfs`?


Thanks,

Paul

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.8-1-amd64 root=/dev/mapper/sde2_crypt ro quiet noisapnp

-- /etc/crypttab
# <target name> <source device>         <key file>      <options>
sde2_crypt      /dev/sde2               none            luks,discard

[…]

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.8-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/dash

Versions of packages cryptsetup depends on:
ii  cryptsetup-bin         2:1.4.3-4
ii  debconf [debconf-2.0]  1.5.49
ii  dmsetup                2:1.02.77-1
ii  libc6                  2.17-2

Versions of packages cryptsetup recommends:
ii  busybox                                 1:1.20.0-8
pn  console-setup                           <none>
ii  initramfs-tools [linux-initramfs-tool]  0.112
ii  kbd                                     1.15.5-1

Versions of packages cryptsetup suggests:
pn  dosfstools              <none>
ii  liblocale-gettext-perl  1.05-7+b1

-- debconf information:
  cryptsetup/prerm_active_mappings: true

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to