News for hackers. Stuff that matters.

A comment on Broken by design: systemd. Parent comment

Re:Broken by design: systemd by Jasper_ on Sunday February 09, 2014 @09:43PM (#7208782)
The only Plymouth-specific code I see in systemd is related to asking the user questions at boot-up time, like their mount password, and it works by sending a socket message to a socket plymouth opens, and successfully falls back if it doesn't exist.

I don't see any plymouth-related services or unit files hardcoded. I do, however, see a NEWS-related entry from the v186 release: http://cgit.freedesktop.org/systemd/systemd/tree/NEWS#n1775

[ Parent | on HN ]
Re:Broken by design: systemd by ploxiln on Sunday February 09, 2014 @10:42PM (#7208974)
there are no unit files, but there are units:

[plo@plo-air ~]$ systemctl --all | grep plym

plymouth-quit-wait.service masked inactive dead plymouth-quit-wait.service

plymouth-start.service masked inactive dead plymouth-start.service

[ Parent | on HN ]
Re:Broken by design: systemd by Jasper_ on Monday February 10, 2014 @01:26AM (#7209474)
On my system, those units do have unit files, and they're provided by the Plymouth package. I couldn't find any reference to "plymouth-quit-wait" in the systemd source code, so those strings have to be coming from somewhere. Are you sure you don't have a unit file at /usr/lib/systemd/systemd/plymouth-quit-wait.service ?
[ Parent | on HN ]