[Splashy-devel] Commit UNIX sockets

[Otavio Salvador]

Tim Dijkstra <newsuser at famdijkstra.org> writes:

>> Yes, indeed. But in that case we might have a way to handle the return
>> status as we do nowadays and use it to progress the bar. Just in case
>> we lack the lsb support for a script.
>
> ? I don't understand what you're trying to say...
>
> I was just thinking that we do not need all scripts to use the lsb-functions,
> it just means we have less granular updating of the progress bar. If for example
> we have four init scripts, and the first one hasn't but second has lsb support.
> We just update the progress bar to 50% after the second one. If the first one
> gains lsb-functions we will have a smoother bar (0, 25%, 50%, etc), but
> as long as a few scripts use log_msg, it will work non the less.

Yes but we need to detect which ones already finished (using return
status of pid) and then do  the math to update the progressbar. Just it.

>> That's the way usplash works nowadays but it's very simple and now so
>> flexible as splashy is and can be made. Nevertheless I think we can
>> use this information in verbose console mode instead of read tty
>> directly.
>
> I was not saying it should be the standard mode, but it should be configurable.
>
> Does usplash has a progress bar? If they do we can see how they calculate the
> progress bar steps.

Yes, they have it. I didn't check how they do that. Luis?

-- 
        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."