removing plymouth

[Ahmad Samir]

On 11/07/14 08:27, Balint Szigeti wrote:
> 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 at 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 :)
>
>
>

As has been said removing the plymouth packages shouldn't prevent the 
system from booting (you probably will need to rebuild the initramfs and 
remove "rhgb quiet" from the kernel cmd line).

Note that the times in the output don't necessarily mean that 
plymouth-quit-wait.service is the reason the boot is slow, from the man 
page:

<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>
"systemd-analyze blame" prints a list of all running units, ordered by 
the time they took to initialize. This information may be used to 
optimize boot-up times. Note that the output might be misleading as the 
initialization of one service might slow simply because it waits for the 
initialization of another service to complete.
<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

-- 
Ahmad Samir