Plymouth users requested

[CentralWare]

I've hunted (google as well as here) and still have yet to figure out either what I'm doing wrong or if there's something missing which isn't being complained about.

Environment:
     VMWare running TC4
     core.gz has been remastered to include the compiled plymouth 0.9.0 and updated rcS
     The only changes made to plymouth were the etc/plymouth/plymouth.conf indicating a theme
     init.d/rcS calls ldconfig and then plymouthd --mode=boot --attach-to-session --pid-file=... followed by plymouth --show-splash right before the call to tc-config.  AFTER tc-config's call I'm calling plymouth --quit which was a reasonably sensible location to shut down plymouth for testing.

     The problem is...  you'd never otherwise know plymouth was even installed.  (Not even text-mode as a fall-back.)

Compiling:
     Some missing resource for building documents flagged an error, so instead of digging, I added --exclude-documentation
     Other than needing to create a sym-link to /local/lib/libply-splash-core.so.2.1.0 (so.2 was missing) things went without a hitch.
     Dependencies were bash and udev-lib for runtime and udev-dev for compilation.

Code: [Select]

./configure --exclude-documentation
make
sudo make install
...followed by running find --newer to get the files and directory structure

Remastering:
     I have a system which is set up to build my remasters for me, using a fashion similar to slip-streaming to embed extensions into the image.  The following are on that list: acpid dropbear e2fsprogs ethotool firmware hddtemp nfs-utils vblade wireless_tools wireless-KERNEL wqa_gui Xorg-7.6 Xprogs Xlibs alsa icewm-1.3.7* idesk bash udev-lib and of course, plymouth*.
* non-repo extensions
*2 embedding also includes any known dependencies not within the list
*3 A command is placed in tc-config which launches files in tce.installed right before any tcz's are loaded, though currently there are none.

Boot menu:
APPEND initrd=/tce/boot/coretest.gz syslog norestore base pause
     "base" is only needed to help prevent this test environment from detecting my persistent tce= from an alternate core.gz boot item.
     Note: I doubt is has any bearing, but ext/syslinux is using vesamenu

The system boots perfectly fine and drops me to the Xorg based desktop, but like I said, you'd never know we were even attempting to fire up plymouth as there's no complaints during boot and not a single notation in the logs.

NOTE: While I'm writing this I'm testing different things to make sure I'm not posting due to an oversight.  I just had an odd situation take place which I'm thinking is related.  While typing, the VM is sitting at the PAUSE from the boot code and I wasn't sure which screen I was on (this one or the VM) so I went to press <CTRL>+<ALT> to release the mouse from the VM but before I hit <ALT> the screen went blank and had three progress indicator place-holders ( % [] [] ) toward the bottom-middle of the screen.  By pressing ENTER it closed and I was sent to the desktop...  so unless I'm mistaken, plymouth is in fact running... just is limbo somewhere.

Any ideas as to where to look?