tags 452462 - patch severity 452462 important thanks Thank you for your feedback. It is very motivating to hear from other testeres of insserv.
[Martin Braure de Calignon] > According to /usr/share/doc/sysv-rc/README.runlevels.gz #6 in > runlevel 6 and 0 scripts begin with S?? should be rename in the > future to K1?? that mean S scripts should be execute after K ones. Actually, it reads: In the future, the /etc/rc6.d/SXXxxxx scripts MIGHT be moved to /etc/rc6.d/K1XXxxxx for clarity. This is probably not a usable solution, as most systems using the sequence number demands that they are two digits. > in /usr/sbin/update-bootsystem-insserv you have in convert_rc_s_to_k function > : > mv $target/etc/rc$runlevel.d/$link > $target/etc/rc$runlevel.d/K$seq$service > instead of > mv $target/etc/rc$runlevel.d/$link > $target/etc/rc$runlevel.d/K1$seq$service > > this make my system launching init.d/reboot as first init script > when I reboot or halt. The bug you are describing is real, that the shutdown sequence is slightly incorrect, but the fix will not work properly with insserv, as insserv require the sequence number to be only two digits. The real bug here is that insserv is sometimes confused when using the *-stop dependency information, and fail to generate a correct shutdown and halt sequence. This is why enabling dependency based boot is still an exerimental feature, hidden deep inside the postinst script. I'm working with upstream to try to figure out why this do not work as expected. And, I am reducing the severity to important, as I believe the sysadmin activating dependency baased boot must follow the instructions and take responsibility for any breakage. Or to quote the text displayed when asking if the feature should be enabled when running "BAD_INSSERV_HACKER=true dpkg-reconfigure insserv": WARNING: It is very hard to revert this change. Reinstallation is probably required to stop using the dependecy based boot system. This is an experimental feature, and is only intended for testing of insserv. Admins deciding to enable it after reading this text get to keep all the pieces if it break. I'm lovering the severity to important because of this. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
