The cryptroot script always uses plymouth if present (plymouth is installed by default on Ubuntu).
Unfortunately this prevents to unlock an encrypted root from console (e.g. via SSH).
Changes in /usr/share/initramfs-tools/scripts/local-top/cryptroot
- new parameter "noplymouth": possible to use during boot time to avoid usage of plymouth even if present
- kill all plymouth processes with "ask-for-password" after encrypted root is available
New file /usr/share/initramfs-tools/hooks/cryptroot_unlock.sh
- creates /bin/unlock script in initramfs to define correct PATH and call cryptroot script with correct parameter
- creates /etc/motd file in initramfs to inform user about unlock script
The cryptroot script always uses plymouth if present (plymouth is installed by default on Ubuntu).
Unfortunately this prevents to unlock an encrypted root from console (e.g. via SSH).
Changes in /usr/share/ initramfs- tools/scripts/ local-top/ cryptroot
- new parameter "noplymouth": possible to use during boot time to avoid usage of plymouth even if present
- kill all plymouth processes with "ask-for-password" after encrypted root is available
New file /usr/share/ initramfs- tools/hooks/ cryptroot_ unlock. sh
- creates /bin/unlock script in initramfs to define correct PATH and call cryptroot script with correct parameter
- creates /etc/motd file in initramfs to inform user about unlock script
Kind regards
Maddes