Bug#385730: marked as done (usplash: Fail to start because /dev/null is missing)
Your message dated Thu, 7 Sep 2006 13:23:10 +0200
with message-id <20060907112310.GK4868@baikonur.stro.at>
and subject line Bug#385730:
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: usplash
Version: 0.3e
Severity: important
Tags: patch
I just tested usplash in qemu using the latest sid packages and kernel
2.6.17. It failed to start complaining that /dev/null was missing.
I'm not sure why, but a fix is to create the device in the
init-top/usplash script before starting usplash. Hree is a patch to
enable it. I tested with it, and it solved the problem. It might be
an idea to add some if-test around it to only try to create /dev/null
if it is missing.
--- /usr/share/initramfs-tools/scripts/init-top/usplash.orig 2006-09-02 17:55:04.000000000 +0200
+++ /usr/share/initramfs-tools/scripts/init-top/usplash 2006-09-02 17:52:43.000000000 +0200
@@ -27,6 +27,10 @@
done
if [ $SPLASH = "true" ]; then
+ # Make sure /dev/null is available when usplash tries to start
+ mknod /dev/null c 1 3
+ chmod a+rw /dev/null
+
/sbin/usplash -c &
sleep 1
fi
Friendly,
--
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
On Thu, Sep 07, 2006 at 12:35:11PM +0200, David Härdeman wrote:
> Isn't this a dupe of bug #385641 which is fixed by now?
>
> --
> David Härdeman
yes, closing
--
maks
--- End Message ---
Reply to: