$ systemd-analyze blame 37.724s plymouth-quit-wait.service 29.148s accounts-daemon.service 27.960s firewalld.service 27.861s avahi-daemon.service 27.720s chronyd.service Just to make you feel better about your system :)

« HTML content follows » On Fri, 2014-07-11 at 06:49 -0400, Sam Varshavchik wrote: > > Ed Greshko writes: > > > On 07/11/14 13:11, Balint Szigeti wrote: > > > > Can somebody tell me what would happen if I remove Plymouth packages? I >    > > know it handles the boot screen and the user interaction during boot. > > > Does it mean, if I remove this package I can't examine what happened   > > during the boot or I can not boot? > > > > > You'll be able to boot just fine.  You'll just see all the "OK"s scrollin > g   > > by as the various components are started. > > > > Not sure what you're thinking the gain will be to remove it. > > If plymouth is installed on one of my servers, plymouth gets stuck about   > half the time, and nevers goes away. > > > One of my laptops, that still has plymouth installed, still manages to lock >    > up maybe 3% of the time. On that laptop, plymouth hasn't yet reached the   > annoyance level needed to remove it. > > Some kind of a hardware-dependent race condition in plymouth. > Could you give me more information about it? How can we determine those HWs?

On 07/11/14 13:11, Balint Szigeti wrote: > Can somebody tell me what would happen if I remove Plymouth packages? I know it handles the boot screen and the user interaction during boot. > Does it mean, if I remove this package I can't examine what happened during the boot or I can not boot? You'll be able to boot just fine. You'll just see all the "OK"s scrolling by as the various components are started. Not sure what you're thinking the gain will be to remove it.

On Fri, 2014-07-11 at 13:41 +0800, Ed Greshko wrote: > On 07/11/14 13:11, Balint Szigeti wrote: >> Can somebody tell me what would happen if I remove Plymouth packages? I know it handles the boot screen and the user interaction during boot. >> Does it mean, if I remove this package I can't examine what happened during the boot or I can not boot? > > You'll be able to boot just fine. You'll just see all the "OK"s scrolling by as the various components are started. > > Not sure what you're thinking the gain will be to remove it. > > -- > If you can't laugh at yourself, others will gladly oblige. $ systemd-analyze blame 10.661s systemd-cryptsetup@luks\x2d9ea31b69\x2d8769\x2d4bf1 \x2d897d\x2d67ecf8d4b0be.service 9.862s plymouth-quit-wait.service 9.743s accounts-daemon.service 8.427s firewalld.service improving the boot time :)

On Fri, 2014-07-11 at 13:41 +0800, Ed Greshko wrote: > On 07/11/14 13:11, Balint Szigeti wrote: > > Can somebody tell me what would happen if I remove Plymouth packages? I know it handles the boot screen and the user interaction during boot. > > Does it mean, if I remove this package I can't examine what happened during the boot or I can not boot? > > You'll be able to boot just fine. You'll just see all the "OK"s scrolling by as the various components are started. > > Not sure what you're thinking the gain will be to remove it. > > -- > If you can't laugh at yourself, others will gladly oblige. $ systemd-analyze blame 10.661s systemd-cryptsetup(a)luks\x2d9ea31b69\x2d8769\x2d4bf1\x2d897d\x2d67ecf8d4b0be.service 9.862s plymouth-quit-wait.service 9.743s accounts-daemon.service 8.427s firewalld.service improving the boot time :)

Can somebody tell me what would happen if I remove Plymouth packages? I know it handles the boot screen and the user interaction during boot. Does it mean, if I remove this package I can't examine what happened during the boot or I can not boot?