Your message dated Tue, 12 Aug 2008 16:02:28 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Checks for usplash command line option have returned
has caused the Debian Bug report #448981,
regarding Checks for usplash command line option have returned
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
448981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448981
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: usplash
Version: 0.5.2-3
Severity: normal
I think the decision from #397954 and #383327 was that usplash would be
enabled by default if installed and unless the system was booted with
nosplash.
It seems some checks for "splash" in /proc/cmdline have crept back in
(see /etc/init.d/sendsigs and /etc/init.d/usplash, in the stop action).
I guess these need to be fixed to do something like:
if type usplash_write && grep -qv nosplash /proc/cmdline; then
/* Do something...like start usplash */
fi
--
David Härdeman
--- End Message ---
--- Begin Message ---
Version: 0.5.19-2
[David Härdeman]
> It seems some checks for "splash" in /proc/cmdline have crept back
> in (see /etc/init.d/sendsigs and /etc/init.d/usplash, in the stop
> action). I guess these need to be fixed to do something like:
The code in sendsigs is no longer there since initscripts version
2.86.ds1-57, and the test in init.d/usplash is correct in version
0.5.19-2. Because of this, I am closing this bug as fixed.
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
