Control: severity -1 important
Cyril Brulebois <kibi@debian.org> (24/11/2012):
> even though wheezy beta 4 images got built against a fixed
> cryptsetup, the first boot-up with an encrypted LVM might lead to
> the needed for typing the passphrase in qwerty.
>
> I guess it might depend on what components are selected in tasksel,
> but that's the case at least with netinst and no desktop
> environment.
Here’s the relative order of console-setup/cryptsetup/u-i:
| $ egrep '(console-setup|cryptsetup|update-initramfs)' syslog-encrypted-lvm.log|egrep '(Install|initramfs)'
| Dec 26 16:50:13 in-target: kbd console-setup initramfs-tools linux-initramfs-tool busybox
| Dec 26 16:50:17 in-target: debconf (developer): <-- SUBST debconf-apt-progress/info DESCRIPTION Installation de libcryptsetup4
| Dec 26 16:50:17 in-target: debconf (developer): ----> DATA debconf-apt-progress/info description Installation de libcryptsetup4
| Dec 26 16:50:17 debconf: --> DATA debconf-apt-progress/info description Installation de libcryptsetup4
| Dec 26 16:50:17 in-target: debconf (developer): <-- SUBST debconf-apt-progress/info DESCRIPTION Installation de cryptsetup-bin
| Dec 26 16:50:17 in-target: debconf (developer): ----> DATA debconf-apt-progress/info description Installation de cryptsetup-bin
| Dec 26 16:50:17 debconf: --> DATA debconf-apt-progress/info description Installation de cryptsetup-bin
| Dec 26 16:50:17 in-target: debconf (developer): <-- SUBST debconf-apt-progress/info DESCRIPTION Installation de cryptsetup
| Dec 26 16:50:17 in-target: debconf (developer): ----> DATA debconf-apt-progress/info description Installation de cryptsetup
| Dec 26 16:50:17 debconf: --> DATA debconf-apt-progress/info description Installation de cryptsetup
| Dec 26 16:50:34 in-target: update-initramfs: deferring update (trigger activated)
| Dec 26 16:52:20 in-target: update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
| Dec 26 16:53:11 in-target: debconf (developer): <-- SUBST debconf-apt-progress/info DESCRIPTION Installation de console-setup-linux
| Dec 26 16:53:11 in-target: debconf (developer): ----> DATA debconf-apt-progress/info description Installation de console-setup-linux
| Dec 26 16:53:11 debconf: --> DATA debconf-apt-progress/info description Installation de console-setup-linux
| Dec 26 16:53:12 in-target: debconf (developer): <-- SUBST debconf-apt-progress/info DESCRIPTION Installation de console-setup
| Dec 26 16:53:12 in-target: debconf (developer): ----> DATA debconf-apt-progress/info description Installation de console-setup
| Dec 26 16:53:12 debconf: --> DATA debconf-apt-progress/info description Installation de console-setup
Some ways to go forward:
1. patch console-setup's postinst to detect when cryptsetup is
installed, to kick an update-initramfs run.
2. patch some d-i component to manually trigger an initramfs update
when cryptsetup and console-setup are installed; maybe some
finish-install thing?
[3. please submit your ideas]
Both could work, I guess. Maybe the former would be better, since one
would want an initramfs update in case the default keymap is changed?
The latter would be slightly less intrusive, so might be my favorite
here.
> It might have to do with the order in which components (cryptsetup,
> console-setup, and friends) are installed, since just running:
> update-initramfs -u -k all
>
> and rebooting fixes that.
Diffing the contents of the initramfses, we have those extra files in
the rebuilt one:
/bin/loadkeys
/etc/boottime.kmap.gz
which confirms the above diagnosis: u-i needs to be run after c-s is
installed.
I'll play with a local patch implementing the second proposal for the
time being; comments more than welcome.
Mraw,
KiBi.
Attachment:
signature.asc
Description: Digital signature