[Splashy-devel] Bug#485307: Bug#485307: splashy starts too late during startup/shutdown

[Luca Capello]

Hi Petter!

On Tue, 10 Jun 2008 18:04:18 +0200, Petter Reinholdtsen wrote:
> [Ritesh Raj Sarraf]
>> So I think maybe the problem is with insserv.
>
> I suspect you CC me to see if I have a comment about the provided LSB
> header.  Did you have a look at usplash and how it is done there?  It
> works.

As the submitter stated, the problem here is not that splashy doesn't
work, but that it's started too late *after* he entered the LUKS
passphrase [1].  I know this situation because I found the same problem.
And to me, too, this seems a bug in insserv.

I just tested on a clean sid chroot:

1) without insserv
   =====
   root at gismo:/# ls -1 /etc/rcS.d/
   [...]
   S02mountkernfs.sh
   S03splashy
   S03udev
   [...]
   root at gismo:/#
   =====

2) with insserv
   =====
   root at gismo:/# ls -1 /etc/rcS.d/
   [...]
   S02hostname.sh
   S03mountkernfs.sh
   S04udev
   [...]
   S16splashy
   S16stop-bootlogd-single
   root at gismo:/#
   =====

Thus, insserv doesn't respect splashy's directives.

FYI, if I move S16splashy to S04splashy I get what is expected: splashy
is started as soon as possible.

Thx, bye,
Gismo / Luca

Footnotes: 
[1] FWIW at least splashy_0.3.10-2 correctly manages LUSK passhphrases,
    so splashy can be enabled in initramfs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 314 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20080921/0e217973/attachment.pgp