Bug#358452: [Pkg-cryptsetup-devel] Bug#358452: initramfs cryptroot
functionality
David Härdeman
david at 2gen.com
Tue May 9 20:06:30 UTC 2006
On Tue, May 09, 2006 at 12:12:40AM +0300, Riku Voipio wrote:
>On Mon, May 08, 2006 at 10:42:59PM +0200, David Härdeman wrote:
>> Unfortunately, simply changing the module detection to use cryptsetup
>> status does not work in the installer as the cryptsetup devices are not
>> available in the /target chroot.
>
>I started work for this on #365747. Would we actually need cryptX nodes
>as well?
Probably if we want the initramfs generated in the final parts of
debian-installer to work with luks without having to use one of the
other solutions I listed below...
>> I'll need to take a look at this, d-i might have to add the modules
>> manually to /etc/mkinitramfs/modules, or perhaps all crypto modules
>> should be included (in keeping with the mkinitramfs tradition which
>> seems to be to try to create as general an image as possible).
>
>I have been trying to think about the hook as used after install. I'd
>rather not rely on d-i to add the modules, since initramfs can be
>regenerated at anytime.
Yes, I agree that the hook needs to work under both circumstances...
buth the d-i chroot is quite a special case since it lacks some things
which can usually be assumed. But your fix in #365747 with the crypt
nodes would probably suffice.
Re,
David
More information about the Pkg-cryptsetup-devel
mailing list