[Pkg-sysvinit-devel] Bug#633835: Bug#633835: Remove dead splash support code

[Michael Biebl]

Am 14.07.2011 09:44, schrieb Petter Reinholdtsen:
> [Michael Biebl]
>> Neither splashy nor plymouth is using this API.
> 
> How do splashy and umount handle interactive queries (ie requests for
> password or the fsck questions) and the fsck progress status?

I can't tell. I've CCed the splashy and plymouth maintainers. They should know more.

From what I can see though, the current splash code doesn't really handle those
case either, e.g. there no interaction between fsck and the splash system, i.e.
no input and progress updates, or does it?

>> So it only adds unnecessary complexity and slows down boot.
> 
> Make sense to me, given that there is an alternative in place to solve
> the same problem.  If not, I suspect it is better to get splashy and
> plymouth to use this API. :)

I've been checking the vcs log, and if I checked correctly, this splash code has
been there for over 5 years. It has never been used since then.
When usplash was around, it had it's own splash support code in initscripts.
Why were splashy and later plymouth never updated to use the splash API provided
by initscripts? Was there never a discussion between the sysvinit maintainers
and the splashy/plymouth maintainers or was the API deemed as not sufficient?

There is also the problem, that starpar does not support progress information.

I guess the functionality can be broken down into three different parts:

1.) Progress information about started services
2.) Quering for input (unlocking SSL certs in apache or openvpn)
3.) Fsck progress information and input handling.


(1) seems to be broken in default setups as startpar does not support that and
it is not actually clear if splashy/plymouth need that progress information or
if they get that via other means.

(2) that's unsolved problem atm.

(3) looks like an unsolved problem too. There is no progress information passed
on and also no interaction between fsck and the splash system.


Given that the current splash code in initscripts doesn't solve any realworld
problem and has been there unused for several years, I proposed this patch.

But maybe something can be worked out with the splash system maintainers which
is actually useful to them.

Fabo, Daniel please speak up and let us know what you need in splashy and
plymouth for a tighter integration.

Because if you don't plan to use any of those facilities (either because they
are unsufficient or unnecessary), it is no point in keeping them around.

Cheers,
Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20110714/a175c9de/attachment.pgp>