Hello Ryan,<br>
<br>
(i have cc the splashy-users list for historical purpose. Read on... )<br><br><div><span class="gmail_quote">On 11/29/05, <b class="gmail_sendername">Ryan Quinn</b> <<a href="mailto:ryan@isptec.net">ryan@isptec.net</a>
> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Greetings,<br><br>I am the project leader of the Symphony OS distro<br>(<a href="http://www.symphonyos.com">
http://www.symphonyos.com</a>) and recently I have been playing around with<br>integrating splashy with our knoppix base system. As you may know,<br>knoppix doesnt quite boot like a standard debian box, rather most work<br>
is done via knoppix-autoconfig. I have modified the isolinux.cfg to run<br>in a proper fb mode for splashy and then added (splashy boot;) to the<br>knoppix-autoconfig and it does indeed start (had some problems with the<br>
splashscreen showing up in the upper left at 640x480 so I just switched<br>the framebuffer to 640x480 and it looks ok).</blockquote><div><br>
<br>
Good to know. Knoppix with splashy is a good combo. I know knoppix uses
another approach to user-space bootsplashing, but, I found it to be too
complicated when we first researched other boot splashing projects.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I have a couple quick questions...<br><br>1.) Have you managed to get a statically compiled binary together for
<br>splashy? with this I could add it to knoppix's minirt.gz rather than<br>having to wait until the cd is found, mounted and unionfs loaded.</blockquote><div><br>
<br>
Splashy has been compiled statically since version 0.1.5.svn11 or
so. Check our svn code. Essentially you can do a svn
checkout. and then use:<br>
<br>
./autogen.sh --prefix=/ --enable-debug # debugging is optional of course<br>
make<br>
make install<br>
<br>
that should do it. But, creating a debian package is easier and cleaner:<br>
<br>
debuild -uc -us<br>
dpkg -i ../splashy*.deb ../splashy-themes*.deb<br>
<br>
To ensure that splashy is statically compile:<br>
<br>
ldd /sbin/splashy<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2.) How does splashy know when to increment the progress meter. I get no<br>progress meter at all (it draws the outline but it doesnt move). Is it
<br>looking for specific output durring boot? If so, I will need to emulate<br>what it needs in the knoppix-autoconfig (would need to change it there<br>rather than in splashy so it will work when installed like a regular
<br>debian system too).</blockquote><div><br>
<br>
splashy writes the word "progress NN" to /etc/splashy/splashy.fifo. <br>
<br>
Example: echo "progress 66" > /etc/splashy/splashy.fifo<br>
That will increase the progress bar to 66%<br>
<br>
Of course, when writing to a fifo, the console input will be "grabbed"
until a program reads from the fifo. You would then need to run:<br>
cat /etc/splashy/splashy.fifo<br>
Or have splashy running and login via ssh... You would figure it out.<br>
<br>
The fifo (named pipe) location is configured via
/etc/splashy/config.xml and /etc/default/splashy. The latter file is
used by the initrc scripts. The XML file is the one that the splashy
binary uses. Check the man page.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">3.) If I can not easily fool splashy so it shows the progress meter can<br>i just run "splashy test" instead when booting without any big problems
<br>(the moving progress meter that just loops over and over would be better<br>than nothing).</blockquote><div><br>
<br>
The progresbar can be turn on and off by e/a theme's config.xml
file. check the sample config.xml files for the themes and you
will understand. During "splashy test" the progressbar is updated
internally in a tight loop within one splashy thread (fork'ed child).<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks for your time, I wouldnt have emailed but I simply could not find<br>the info on your site, mailing list archives, or elsewhere.
</blockquote><div><br>
And I'm glad you asked. We might need to add this to the wiki page then ;-)<br>
<br>
You could do that yourself by simply creating an account in our Wiki page:<br>
<br>
<a href="http://splashy.alioth.debian.org/wiki">http://splashy.alioth.debian.org/wiki</a><br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Sincerely,<br>Ryan Quinn<br>Project Manger<br>Symphony OS<br><a href="http://www.symphonyos.com">
http://www.symphonyos.com</a><br></blockquote></div><br>Cheers.<br clear="all"><br>-- <br>----)(----- <br>Luis M<br>System Administrator<br><a href="http://Kiskeyix.org">Kiskeyix.org</a> <br><br>"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<br><br>No .doc: <a href="http://www.fsf.org/philosophy/no-word-attachments.es.html">http://www.fsf.org/philosophy/no-word-attachments.es.html</a>