Package: splashy Version: 0.3.0 Severity: normal There are currently two ways to configure if splashy should be run or not: the absence/presence of the splash boot parameter and ENABLE=(0|1) in /etc/default/splashy. It seems though, that the "splash" boot parameter only has influence on the initramfs part of splashy, the /etc/init.d/splashy script does not evaluate this parameter and vice versa (the initramfs script only evaluates the boot parameter but not ENABLE). I find the usage of ENABLE in /etc/default/splashy misleading and superfluous and would recommend to only use the splash boot parameter consistently in the initramfs and init script. E.g. it is quite strange if you remove splash from the boot prompt and the initramfs does not start but the init script does (ENABLE=1). Or if you set ENABLE=0, which disables the init script but not the initramfs. Again, I think the ENABLE parameter is not needed and only causes confusion. Using the splash boot parameter solely is more flexibe (than ENABLE) and consistent.
Cheers, Michael -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.20 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages splashy depends on: ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libglib2.0-0 2.12.6-2 The GLib library of C routines ii libmagic1 4.19-1 File type determination library us ii libsplashy0 0.3.0 Library to draw splash screen on b ii zlib1g 1:1.2.3-13 compression library - runtime Versions of packages splashy recommends: ii lsb 3.1-23 Linux Standard Base 3.1 support pa ii lsb-base 3.1-23 Linux Standard Base 3.1 init scrip -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
