As for "no case in which plymouth is not used": I'm afraid I grossly misunderstand when plymouth is used.
I experimented the "command-line" behavior I described above when booting in "recovery mode".
Is plymouth also used in "recovery mode" or when one removes the 'splash' parameter from the kernel boot options?
cryptsetup "provisions" for when plymouth is not installed/active; in '/lib/cryptsetup/cryptdisks.functions', function 'do_luks':
[...]
if [ -x /bin/plymouth ] && plymouth --ping; then KEYSCRIPT="plymouth ask-for-password --prompt" keyscriptarg=$(printf "$keyscriptarg") else KEYSCRIPT="/lib/cryptsetup/askpass"
fi
[...]
But not a big issue I agree. Merely an "esthetic" one.
Hello Steve,
Thanks for your comments.
As for "no case in which plymouth is not used": I'm afraid I grossly misunderstand when plymouth is used. p/cryptdisks. functions' , function 'do_luks':
KEYSCRIPT= "plymouth ask-for-password --prompt"
keyscriptarg =$(printf "$keyscriptarg")
else
KEYSCRIPT= "/lib/cryptsetu p/askpass"
I experimented the "command-line" behavior I described above when booting in "recovery mode".
Is plymouth also used in "recovery mode" or when one removes the 'splash' parameter from the kernel boot options?
cryptsetup "provisions" for when plymouth is not installed/active; in '/lib/cryptsetu
[...]
if [ -x /bin/plymouth ] && plymouth --ping; then
fi
[...]
But not a big issue I agree. Merely an "esthetic" one.