Bug#383327: is this bug still legit?

[Arias Hung <arias@m-a-g.net>]

On Wed, 16 Aug 2006, Danial Payne <debian@gepro.cz) delivered an accurate usplash bug report:

> Installed Usplash is active only on system shutdown. Two action are                               missing the installation script to activate it on system boot.
>
>  1. Add 'splash' to the boot commandline else Usplash will not start
>  2. Delete the link /etc/rcS.d/S48console-screen.sh else Usplash gets 
>     terminated prematurely by console-screen.sh                                  
>
>   /etc/init.d/usplash start will call console-screen.sh at the end of boot process anyway.



I've noticed that splash=silent is now auto added to the boot commandline.

However, S48console-screen.sh in rcS.d is still present.  Is this premature
termination intentional?

If S48console-screen.sh is deleted, console-screen.sh is not called by usplash until the very end of runlevel 2 at rc2.d/S98usplash.

Is it accurate to manually delete or at least divert S48console-screen.sh while usplash is installed? And if so, why hasn't this procedure been added to the usplash postinstall script?

Please let us know.

Thanks for the time you've put into this aesthetically beautiful contribution!

A

Attachment: pgpkB1udhRJx4.pgp
Description: PGP signature