Package: splashy Version: 0.3.8-1 Severity: normal Hi,
after trying both splashy and usplash, I must say that usplash does a significantly better job in capturing init script output. When booting a rather minimal Debian sid with splashy, all I see is: Starting Boot splash manager: splashy Starting the hotplug events dispatcher: udevd Reloading OpenBSD Secure Shell server configuration: sshd Starting OpenBSD Secure Shell server: sshd Starting internet superserver: inetd Starting deferred execution scheduler: atd Starting periodic command scheduler: crond usplash, otoh, shows a lot about file systems being mounted etc, which allows one to see better what's going on. For example, when a crypto partition is to be mounted using dm-crypt and LUKS, one just has to guess when to enter the key, while with usplash, you see a "setting up $LV_NAME" before the boot process prompts (invisibly, of course) for the key. That being said, splashy is of course the much better option and rocks, compared to usplash. Greetings Marc -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages splashy depends on: ii initramfs-tools 0.92 tools for generating an initramfs ii libc6 2.7-10 GNU C Library: Shared libraries ii libdirectfb-1.0-0 1.0.1-8 direct frame buffer graphics - sha ii libgcc1 1:4.3.0-3 GCC support library ii libglib2.0-0 2.16.3-2 The GLib library of C routines ii libmagic1 4.23-2 File type determination library us ii libsplashy1 0.3.8-1 Library to draw splash screen on b ii lsb-base 3.2-11 Linux Standard Base 3.2 init scrip ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime splashy recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
