[Splashy-devel] splashy talking over unix domain sockets

[Luis]

Tim,

Follow Otavio's advise. Break "trunk" only of course ...

And yes, we target 2.6.x kernels, but also keeping in mind that some
BSD users have attempted to port Splashy before. So, try to always be
as POSIX as you can be so that you don't break other UNICES.

Keep up the good work.

Now, the bug in initramfs currently is this:

1. splashy opens many filehandles at start
2. splashy closes all uneeded filehandles, but a few things stay
behind: 1 thread listening for keyboard events, 1 thread listening for
events from the FIFO (which opens and close the file in NON-IO block
mode)
3. when init takes over, "something" sends a kill signal to all
processes that started from initramfs. splashy's dfb lib handles this
for us stopping splashy. splashy-init then restarts splashy at
/etc/rcS.d/S01splashy-init (so you see two fade-in effects in
succession)
4. if splashy handles it's own signals (instead of directfb lib) then
the boot process gets stopped and splashy just sits there waiting...
the wait is because something else at /etc/rcS.d changes the fonts of
the console from whatever they were to whatever they should be (UTF8
for some of us -- unicode. Or back to ASCII). console-screen.sh and
some other .sh that I can't recall now... see splashy-init comments

This last thing also happens if splashy is not killed by "something"
after init takes over (pivot_root or whatever it is that switches init
from initramfs to /dev no the real filesystem. see linuxrc)

Hope that helps.

On 8/16/06, Otavio Salvador <otavio at debian.org> wrote:
> Tim Dijkstra <tim at famdijkstra.org> writes:
>
> > * The credential thing only works on linux (and BSDs, but not in the code I wrote now)
> >   Not sure this is a problem actually... Aren't we targeting linux 2.6 only?
>
> I think that we won't use it in others systems besides Linux and BSDs.
>
> > So now for the questions:
> >
> > Is splashy supposed handle strings which are several commands separated
> > by newlines? Looking at the code I think it does now, but my code
> > currently breaks that assumption. It accepts only one command per
> > message (with a maximum size of 1024 char btw).
>
> Looks ok to me. If we need to pass two commands we call it twince.
>
> > Oh, final question, what was the precise symptom of the 'initramfs bug'
> > again?
>
> Splashy itself restart twice and abort when setting fonts.
>
> > So I got commit access to svn, but do you usually sent patches for
> > review? I'm a bit reluctant to just commit and break trunk without
> > discussion first;)
>
> Commit and then we start to fix remaining issues ;-)
>
> --
>         O T A V I O    S A L V A D O R
> ---------------------------------------------
>  E-mail: otavio at debian.org      UIN: 5906116
>  GNU/Linux User: 239058     GPG ID: 49A5F855
>  Home Page: http://www.freedom.ind.br/otavio
> ---------------------------------------------
> "Microsoft gives you Windows ... Linux gives
>  you the whole house."
>
> _______________________________________________
> Splashy-devel mailing list
> Splashy-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/splashy-devel
>


-- 
----)(-----
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