8 May
2018
8 May
'18
6:32 p.m.
Leslie Turriff wrote:
$ dpkg -l | grep plymou
ii libplymouth4:amd64 0.9.2-4
amd64 graphical boot animation and logger - shared libraries
ii plymouth 0.9.2-4
amd64 boot animation, logger and I/O multiplexer
ii plymouth-themes 0.9.2-4
amd64 boot animation, logger and I/O multiplexer - themes
ii plymouth-x11 0.9.2-4
amd64 boot animation, logger and I/O multiplexer - X11 renderer
works great - no issues
AFAIR there was a problem when systemd does not complete/close the target.
I use
ii sysv-rc 2.88dsf-59.9
all System-V-like runlevel change mechanism
ii sysvinit-core 2.88dsf-59.9
amd64 System-V-like init utilities
ii sysvinit-utils 2.88dsf-59.9
amd64 System-V-like utilities
hope this helps
regards
Leslie Turriff
composed on 2018-05-07 05:27 (UTC-0500):
I agree. I wouldn't
mind these folks adding such new stuff to the
distros, except that (as KDE did) they tend to make them at best default,
and at worse mandatory, removing the features we're used to and
(sometimes) replacing them with "improved" ones. :-( If anyone else still has plymouth installed and
can check with top to
confirm plymouth is hogging CPU, that would be worth investigating. I
can confirm this on 2 boxes.
I don't get why anyone thinks Plymouth's basic purpose is more desirable
than the bloat it represents, or useful at all. I've never had it
installed on an openSUSE installation unless maybe when it first appeared
I didn't notice to taboo it. If I did, it was too long ago to remember.
Anywhere else, e.g. Mageia, where Plymouth was not optional,
plymouth.enable=0 went on those kernel cmdlines. At boot time, I don't
need rainbow fluff and spindly or no text instead of nice bold, legible
white on black racing so fast it can't all be read.