You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Ray Strode 8fc93c9a47
build-goo: fix obtuse warning message from autogoo
11 years ago
docs docs: add docbook based man pages 11 years ago
images ship bizcom unconditionally 16 years ago
scripts scripts: make plymouth-update-initrd somewhat more useful 11 years ago
src build-goo: s/INCLUDES/AM_CPPFLAGS/ 11 years ago
systemd-units systemd-units: ensure udevd is started before plymouthd 11 years ago
themes Make contact the default text plugin 11 years ago
.gitignore gitignore: Ignore systemd service and path files. 11 years ago
AUTHORS Add Peter to AUTHORS 16 years ago
COPYING initial import 17 years ago
ChangeLog Put in ChangeLog request to not use ChangeLog 16 years ago
INSTALL Add stub INSTALL file 15 years ago
Makefile.am docs: add docbook based man pages 11 years ago
NEWS initial import 17 years ago
README README: resync from wiki 13 years ago
TODO Add hack to make maintenance mode probably work when 16 years ago
acinclude.m4 [configure] Add AS_AC_EXPAND for configured dirs 15 years ago
autogen.sh autogen.sh: rework to be more buildsystem friendly 13 years ago
configure.ac build-goo: fix obtuse warning message from autogoo 11 years ago

README

plymouth - graphical boot animation and logger


Plymouth is an application that runs very early in the boot process
(even before the root filesystem is mounted!) that provides a graphical
boot animation while the boot process happens in the background.

It is designed to work on systems with DRM modesetting drivers. The idea
is that early on in the boot process the native mode for the computer is
set, plymouth uses that mode, and that mode stays throughout the entire
boot process up to and after X starts. Ideally, the goal is to get rid
of all flicker during startup.

For systems that don't have DRM mode settings drivers, plymouth falls
back to text mode (it can also use a legacy /dev/fb interface).

In either text or graphics mode, the boot messages are completely
occluded. After the root file system is mounted read-write, the
messages are dumped to /var/log/boot.log. Also, the user can see the
messages at any time during boot up by hitting the escape key.

Plymouth isn't really designed to be built from source by end users. For
it to work correctly, it needs integration with the distribution.
Because it starts so early, it needs to be packed into the
distribution's initial ram disk, and the distribution needs to poke
plymouth to tell it how boot is progressing.

plymouth ships with two binaries: /sbin/plymouthd and /bin/plymouth

The first one, plymouthd, does all the heavy lifting. It logs the
session and shows the splash screen. The second one, /bin/plymouth, is
the control interface to plymouthd.

It supports things like plymouth show-splash, or plymouth
ask-for-password, which trigger the associated action in plymouthd.

Plymouth supports various "splash" themes which are analogous to
screensavers, but happen at boot time. There are several sample themes
shipped with plymouth, but most distributions that use plymouth ship
something customized for their distribution.

Plymouth isn't done yet. It's still under active development, but is
used in several popular distros already, including Fedora, Mandriva,
Ubuntu and others. See the distributions page for more information.