hello
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?
Balint
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 07/11/14 14: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@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 :)
Not sure what plymouth-quit-wait.service is....but on one of my systems....
5ms plymouth-quit-wait.service
On Fri, 11 Jul 2014 07:27:51 +0100 Balint Szigeti balint.szgt@gmail.com 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@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 :)
$ 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 :)
On 11.07.2014 08:51, Fred Erickson wrote:
$ 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 :)
$ systemd-analyze blame | grep -m1 [0-9][ms] 9.705s mariadb.service
poma
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@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. <<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
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 scrolling 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.
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 scrolling 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?
Balint Szigeti writes:
« 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?
I have no idea what HW is a problem; or if it's even the hardware. Could be a race condition due to the different software packages. Different modules being started by systemd, in different order.
Hi
On Fri, Jul 11, 2014 at 6:17 PM, Sam Varshavchik wrote:
I have no idea what HW is a problem; or if it's even the hardware. Could be a race condition due to the different software packages. Different modules being started by systemd, in different order
Is there a bug report?
Rahul
Am 12.07.2014 01:10, schrieb Rahul Sundaram:
Hi
On Fri, Jul 11, 2014 at 6:17 PM, Sam Varshavchik wrote:
I have no idea what HW is a problem; or if it's even the hardware. Could be a race condition due to the different software packages. Different modules being started by systemd, in different orderIs there a bug report?
Reminds me of this oldie: https://bugzilla.redhat.com/show_bug.cgi?id=1006386 Klaus
HI
On Sat, Jul 12, 2014 at 2:51 AM, Klaus-Peter Schrage wrote:
Reminds me of this oldie: https://bugzilla.redhat.com/show_bug.cgi?id=1006386
I was looking for a bug report against Plymouth that is current.
Rahul
On Fri, 11 Jul 2014 06:11:49 +0100 Balint Szigeti balint.szgt@gmail.com wrote:
hello
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?
Balint
I removed it years ago, just a preference of mine. No adverse affects.
___ Regards Frank frankly3d.com
-
Ahmad Samir -
Balint Szigeti -
Ed Greshko -
Frank Murphy -
Fred -
Klaus-Peter Schrage -
poma -
Rahul Sundaram -
Sam Varshavchik