First things first, Splashy from initramfs/initrd is work-in-progress.
It still doesn't work correctly (for most users), as explained in the
README and many other sources that relate to splashy...

Now, to get splashy working from initramfs you would need to have at
least one directory that's visible from the ramfs disk as well as from
the real root filesystem once the system boots. in Ubuntu this is
/dev/.initramfs. That means that you would need to set splashy.fifo to
point to that directory and re-make your initramfs before splashy can
work from initramfs. In other words, when init takes over, it needs to
start splashy-init and this will write progress status to whatever
/etc/splashy/config.xml (in the real root filesystem) says that the
FIFO is.

I know this is a bit confusing, but just read it a few times and
hopefully you will understand it. If not, you can always join us at
#splashy on irc.freenode.net... There is always somebody willing to
help there...

About splashy not being started in "shutdown" mode during
reboot/shutdown (runlevel 6 and 0). I'd suggest purging the Splashy
package the way that it's described in the wiki:
http://splashy.alioth.debian.org. Re-install the Splashy package from
Sid and DO NOT change anything ;-) Not until you have read the README
file through and through, as well as the HACKING file in the Splashy
subversion trunk (http://svn.debian.org/wsvn/splashy). You can very
easily break your system when you start changing Splashy around... you
have been warned.

This is not a bug, and it should be closed... I'll leave it open for
now for future reference...

--
----)(-----
Luis Mondesi
*NIX Guru

Kiskeyix.org

"We think basically you watch television to turn your brain off, and
you work on your computer when you want to turn your brain on" --
Steve Jobs in an interview for MacWorld Magazine 2004-Feb

No .doc: http://www.gnu.org/philosophy/no-word-attachments.es.html


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to