> I'm not sure which of plymouth, initramfs-tools or mdadm
> is responsible here.
The answer is mdadm. Plymouth is a boot-time multiplexer; it will not *always* be present in the initramfs, but *when* it is present, it owns the console and other packages need to interface with it if they need to talk to the user. In some cases, such as initramfs-tools' own rescue shell handling, this interfacing consists of calling 'plymouth quit' and restoring the console; in other cases, such as cryptsetup or mdadm, the correct behavior is to use plymouth itself for prompting.
Dmitrijs, could you please take a look at fixing the mdadm initramfs script to use plymouth when present?
Hi Iain,
> I'm not sure which of plymouth, initramfs-tools or mdadm
> is responsible here.
The answer is mdadm. Plymouth is a boot-time multiplexer; it will not *always* be present in the initramfs, but *when* it is present, it owns the console and other packages need to interface with it if they need to talk to the user. In some cases, such as initramfs-tools' own rescue shell handling, this interfacing consists of calling 'plymouth quit' and restoring the console; in other cases, such as cryptsetup or mdadm, the correct behavior is to use plymouth itself for prompting.
Dmitrijs, could you please take a look at fixing the mdadm initramfs script to use plymouth when present?