[pkg-cryptsetup-devel] Bug#779612: Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable

[Gordon Morehouse]

On 03/25/2015 09:29 AM, Jonas Meurer wrote:
[snip]
 >
> Seems like there's some more discussion needed in order to fix the
> reported bug:
>
> a) do we want cryptsetup to recommend plymouth? this way at least
>     for manual installation of cryptsetup, plymouth would be pulled
>     in, fixing destroyed nasty boot-password-prompts introduced that
>     were introduced by the switch to systemd.
>
> b) do we want plymouth to be installed per default on new installs?
>     to my knowledge it's not _required_ for systemd to work, but as
>     soon as an initscript with user interaction is invoked,
>     apparently plymouth is required. This *is* an argument for
>     installing plymouth by default.
>
> c) do we want any of the above to be fixed/changed in time for
>     jessie?

I'm Just A User(tm) but I really think this should be fixed in time for 
jessie, because it looks really, really terrible.  Yes, there's a "fix" 
- if you can get your system booted, which takes me on average 3-5 tries 
with only two interactive password prompts.

If I were a sysadmin and ran into this after installing jessie, I'd 
think strongly about uninstalling it and going with something else.

"It can't even boot right?!" is the first question that came to mind 
after my first install of jessie - really unacceptable UX for a release 
soon to be marked "stable" and a distribution which people have relied 
upon for stability for well over a decade, including myself.

I'll drop it after this, but I urge release maintainers to take the 
above into consideration and fix this in time for jessie.  Thanks for 
all your hard work.

Best,
-Gordon M.