On Wed, 14 Feb 2007 16:19:37 +0100 Michael Biebl <[EMAIL PROTECTED]> wrote:
> Ok, my explanation was maybe not quite accurate. If I use the default > theme it becomes more obvious what happens: > On resume, init-top/splashy runs "splashy boot", which brings up the > default splash screen. > Later, in local-premount/uswsusp, resume thaws the splashy process, > which then shows the nice sleeping penguin. After that, the resume > process goes along as expected. > > Maybe init-top/splashy is the right place to fix this. Before starting > "splashy boot", you should check if we are starting or resuming and only > launch "splashy boot" upon starting. The problem is that we don't know at that point if we are resuming or not. To know that we should have the disks up and running, which means local-premount. I really don't see a way around this issue. The only possibility is moving the start of splashy after that of uswsusp, e.g. to local-premount. This would mean a few seconds delay in the start of splashy, I'm not sure if that's worth it. What do you think? You could see what is the difference by installing splashy after uswsusp. grts Tim
signature.asc
Description: PGP signature
