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 0ade19097f
Add Peter to AUTHORS
16 years ago
images Don't install bizcom logo if alternate logo supplied 16 years ago
scripts Change heuristics in update script for finding which initrd to repack 16 years ago
src Check for truecolor in a more direct way 16 years ago
.gitignore Create new libplybootsplash 16 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 initial import 17 years ago
Makefile.am Use "bizcom" pseudologo for installs that don't specify a logo 16 years ago
NEWS initial import 17 years ago
README Update README 16 years ago
TODO Update TODO 16 years ago
autogen.sh Drop localization bits / use CONFIG_AUX_DIR 17 years ago
configure.ac Expose preferred gradient color stops in configure 16 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.

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/bootmessages.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.

In the scripts/ directory there is a shell script that attempts to unpack an existing
initrd, add plymouth, and pack it back up. It's not a complete solution, though, it's
more for debugging/testing and will probably only work on Fedora based systems.

plymouth ships with two binaries: /usr/libexec/plymouth/plymouthd and /usr/bin/plymouth

The first one, plymouthd, does all the heavy lifting. It logs the session and shows the
splash screen. The second one, /usr/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" plugins which are analagous to screensavers, but
happen at boot time. Currently there are two graphical splash plugins: fade-in,
and spinfinity. There are also two non-graphical plugins which are for text
mode and the details view.

The graphical plugins need a logo image and background color to function.
Distributions are expected to set these up in their packages at ./configure
time, but there are some placeholder values set up if ./configure doesn't get
those options.

Plymouth isn't done yet. It's still under active development and isn't ready for
distros to use as-is. That should change in the near future though.