Quoting from cryptsetup's Debian packaging git:
| commit
06f8c00c908ffd1fa95c4afc78e9cac462d01d91
| Author: Guilhem Moulin <guilhem@debian.org>
| Date: Sat Jul 20 19:18:21 2019 -0300
|
| initramfs: Remove compatibility warnings regarding CRYPTSETUP=[y|n].
|
| The warning was added in 2:2.0.3-1 for the ‘cryptsetup’ package split
| into ‘cryptsetup-run’ and ‘cryptsetup-initramfs’. With the recent
| Buster release we can now move on: cryptsetup is always copied to the
| initramfs when the ‘cryptsetup-initramfs’ package is installed.
Given that we have the cryptsetup-initramfs package in GRMLBASE,
we no longer need to use this.
Closes: https://github.com/grml/grml/issues/82
echo "Rebuilding initramfs"
for initrd in "$(basename $target/boot/vmlinuz-*)" ; do
echo "Rebuilding initramfs"
for initrd in "$(basename $target/boot/vmlinuz-*)" ; do
- if ! CRYPTSETUP=y $ROOTCMD update-initramfs -k "${initrd##vmlinuz-}" -c ; then
- echo "Creating fresh initrd did not work, trying update instead:"
- CRYPTSETUP=y $ROOTCMD update-initramfs -k "${initrd##vmlinuz-}" -u
+ if ! $ROOTCMD update-initramfs -k "${initrd##vmlinuz-}" -c ; then
+ echo "Creating fresh initramfs did not work, trying update instead:"
+ $ROOTCMD update-initramfs -k "${initrd##vmlinuz-}" -u