Find a file
Ray Strode 6e99200ce2 main: split start_boot_splash up into two functions
Right now start_boot_splash loads the theme, then
shows it.

It's going to be useful in the future to preload the
theme, so this commit breaks the two operations out
into two functions, load_theme and show_theme,
and makes start_boot_splash just call those two
functions.
2013-12-06 16:23:45 -05:00
docs docs: add docbook based man pages 2013-10-21 17:56:45 -04:00
images ship bizcom unconditionally 2008-06-22 00:49:24 -04:00
scripts scripts: make plymouth-update-initrd somewhat more useful 2013-10-15 09:52:46 -04:00
src main: split start_boot_splash up into two functions 2013-12-06 16:23:45 -05:00
systemd-units systemd-units: don't timeout the plymouth waiting 2013-11-15 12:41:59 -05:00
themes Make contact the default text plugin 2013-09-23 15:09:07 -04:00
.gitignore gitignore: Ignore systemd service and path files. 2013-02-12 17:32:48 -05:00
acinclude.m4 [configure] Add AS_AC_EXPAND for configured dirs 2009-08-07 16:32:32 -04:00
AUTHORS Add Peter to AUTHORS 2008-06-10 21:59:10 -04:00
autogen.sh autogen.sh: rework to be more buildsystem friendly 2011-10-10 09:16:10 -04:00
ChangeLog Put in ChangeLog request to not use ChangeLog 2008-05-20 15:15:03 -04:00
configure.ac configure: add back --enable-tracing 2013-10-23 15:55:06 -04:00
COPYING initial import 2007-05-08 17:48:00 -04:00
INSTALL Add stub INSTALL file 2009-05-02 01:10:19 -04:00
Makefile.am docs: add docbook based man pages 2013-10-21 17:56:45 -04:00
NEWS initial import 2007-05-08 17:48:00 -04:00
README README: resync from wiki 2011-10-10 10:54:00 -04:00
TODO Add hack to make maintenance mode probably work when 2008-06-30 17:55:15 -04:00

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.