Ray Strode c8e548d5e4 systemd: don't run read-write service from initrd ... the initrd hits the local-fs.target as part of its normal boot process. We used to use local-fs.target as a way of knowing the system / is read-write. This no longer is a valid mechanism. This commit: 1) Stops installing plymouth-read-write service in the initrd 2) Makes it so if it does end up in the initrd it won't be used Related to fedora bug 830482		2012-07-26 13:05:22 -04:00
..
default.cfg	add my scripts directory to git	2007-06-08 12:13:45 -04:00
Makefile.am	[scripts] Don't hardcode LIBEXECDIR and DATADIR paths	2010-03-02 20:08:22 +00:00
new-object.sh	add my scripts directory to git	2007-06-08 12:13:45 -04:00
plymouth-generate-initrd.in	[scripts] Don't hardcode LIBEXECDIR and DATADIR paths	2010-03-02 20:08:22 +00:00
plymouth-populate-initrd.in	systemd: don't run read-write service from initrd	2012-07-26 13:05:22 -04:00
plymouth-set-default-theme.in	set-default-theme: redirect to /dev/null not /null	2010-10-04 09:47:24 -04:00
plymouth-update-initrd	Gut plymouth-update-initrd	2008-10-17 15:49:31 -04:00
plymouth.spec	[splash] Rename libplybootsplash to libply-splash-core	2010-01-13 16:47:09 -05:00