[Michael Biebl] > Try to change the console-screen init screen script: > Change it from > Default-Start: S > Default-Stop: > > to > > Default-Start: 2 3 4 5 > Default-Stop: 0 1 6
Thank you. I'm able to reproduce this, and I consider it a bug. I'm adding a test case to detect this, and will try to find a fix for it. > Please note, that > 1.) it does create the Kill symlinks in 0,1,6. Definitely a bug. The enabled/disabled runlevels on disk are configuration to preserve, while the runlevels listed in the header is only used for first time installation. > 2.) It doesn't remove the S20console-screen.sh symlink from from S, yet > reorders some of the services there. e.g. it moves console-setup to > S20, although console-setup has a Should-Start: console-screen. So > it seems that insserv tries to preserve the symlink, but then > doesn't take it into account for dependency calculation > 3.) It doesn't create the start symlinks for 2,3,4,5. I am not conviced these two are bugs. I find it to be expected behaviour. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
