Package:  console-setup
Version:  1.20
Severity: important
Tags:     patch
User:     [EMAIL PROTECTED]
Usertags: incorrect-dependency

I just checked the boot order in unstable on a machine with dependency
based boot sequencing enabled, and discovered a problem with the
init.d scripts provided in this package.  It was first discovered by
Michael Biebl who reported it to the initscripts-ng-devel mailing
list. The problem is that console-setup and keyboard-setup is not
inserted after the console-screen and keymap scripts in the boot
sequence when dependency based boot sequencing is used, leading to
changed behavior (wrong keyboard and console setting).

Here is a patch to solve this issue, by documenting that console-setup
and keyboard-setup should run after the other scripts.

diff -ur console-setup-1.22.orig/debian/console-setup.console-setup.init 
console-setup-1.22/debian/console-setup.console-setup.init
--- console-setup-1.22.orig/debian/console-setup.console-setup.init     
2008-04-04 21:42:27.000000000 +0200
+++ console-setup-1.22/debian/console-setup.console-setup.init  2008-04-13 
10:53:37.000000000 +0200
@@ -3,6 +3,7 @@
 # Provides:          console-setup
 # Required-Start:    $remote_fs
 # Required-Stop:
+# Should-Start:      console-screen
 # Default-Start:     S
 # Default-Stop:
 # Short-Description: Set console font and keymap
diff -ur console-setup-1.22.orig/debian/console-setup.keyboard-setup.init 
console-setup-1.22/debian/console-setup.keyboard-setup.init
--- console-setup-1.22.orig/debian/console-setup.keyboard-setup.init    
2008-04-04 21:42:27.000000000 +0200
+++ console-setup-1.22/debian/console-setup.keyboard-setup.init 2008-04-13 
10:54:01.000000000 +0200
@@ -3,6 +3,7 @@
 # Provides:          keyboard-setup
 # Required-Start:    mountkernfs udev
 # Required-Stop:
+# Should-Start:      keymap
 # X-Start-Before:    checkroot
 # Default-Start:     S
 # Default-Stop:

Happy hacking,
--
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to