Followup-For: Bug #755194 Michael Biebl wrote: > I don't know why systemd-ask-password-plymouth.path needs > systemd-vconsole-setup.service? Maybe the plymouth maintainers can > elaborate. We disabled vconsole support in systemd since we already > have console-setup in Debian. The plymouth package should probably > adjust this accordingly and probably just drop this
systemd-ask-password-plymouth.path legitimately needs to depend on a working console keymap and font, because it may need to prompt for a passphrase. What if your encryption passphrase depends on characters you cannot type (conveniently or at all) with the default keymap? systemd services can and do depend on other services shipped by systemd. Long-term, we should evaluate what console-setup does that vconsole doesn't or vice-versa, and come up with a single solution that works everywhere, rather than disabling vconsole. There's been serious discussion upstream about adopting the shared-with-X approach of console-setup. But at a minimum, systems may wish to use vconsole instead of console-setup, and it should be available as an option rather than disabled entirely; given that there are already multiple alternative implementations of console-setup, we could then ask whether we get any value out of supporting the other implementations. Short-term, however, I would suggest having console-setup ship a service file that provides systemd-vconsole-setup.service, for compatibility. Plymouth's service will then Just Work without modification. - Josh Triplett -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
