Project

General

Profile

Actions
Copy link

Bug #170

closed

Feature #81: Improve CD boot and shutdown

Splashy does not start in initramfs

Added by Jean-Michel Philippe almost 13 years ago. Updated almost 12 years ago.

Status:
Won't fix
Priority:
Normal
Assignee:
Jean-Michel Philippe
Category:
System
Target version:
2011-05 (Gondwana)
Start date:
05/20/2011
Due date:
05/26/2011
% Done:

100%

Estimated time:
2:00 h
Spent time:
2:00 h

Description

Splashy should start during very early boot since the initramfs option was set. Uncompressing the initramfs file shows that all the required files to start splashy are in the RAM disk file. Using the pause feature of VirtualBox made it possible to shortly see the splashy boot screen during early boot. However it immediately disappeared and was later replaced by messages “Splashy ERROR: connection refused”.

Searching for this message lead to the following thread:

http://lists.alioth.debian.org/pipermail/splashy-users/2008-February/000347.html

It seems that splashy should start after udev to avoid this kind of error. In the initramfs file, both are started from the directory /scripts/init-bottom/ without dependency information, which means splashy should start first due to alphabetical order. So we propose 2 solutions:

  1. add a dependency using the variable PREREQS of the splashy script
  2. rename both scripts by adding numbering before the name

The first solution requires patching the package splashy only, as the second one needs a patch for udev too a priori.

Actions
Copy link

Also available in: Atom PDF