On Wed, 04 Mar 2015 17:56:52 +0100 Michael Biebl <bi...@debian.org> wrote: > Am 04.03.2015 um 17:18 schrieb Gordon Morehouse: > > I've created Bug#779612 [1] to propose that 'systemd-sysv' and 'cryptsetup' > > recommend 'plymouth' in Jessie. There is related discussion in debian-qa[2]. > > > > 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779612 > > 2. https://lists.debian.org/debian-qa/2015/02/msg00051.html > > A recommends in systemd-sysv doesn't help on new installations, since > during debootstrap, recommends are not considered.
I don't think it makes sense for systemd-sysv to recommend plymouth. Suggesting it might make sense, since systemd has specific support for it, but a recommendation seems much too strong. With the new systemd-fsckd, the output of multiple calls to fsck at boot time will not step on each other. And systems that just have an encrypted *root* filesystem should not have an issue either. As far as I can tell, this issue only arises for systems with additional encrypted filesystems. I'm really hoping that problem could be solved via some other sensible mechanism, similar to systemd-fsckd, but even if that case needs plymouth, that's only an argument for cryptsetup to suggest or *perhaps* recommend plymouth, not for systemd-sysv to do so. - Josh Triplett _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
