[Steve Langasek] > So yes, if insserv assumes that all Debian initscripts are LSB init > scripts, it is fundamentally broken.
insserv do not assume this. It uses init.d script dependecy information as provided by the scripts themselves and from files included in insserv, to reorganize the boot sequence according to these dependencies. It also include experimental scripts to run init.d scripts in parallel. I suspect we have a problem of expectations here. The package is in early testing, and need more dependency information before it is ready for general use. It works for me on my four test machines 'rm' has the potential of rendering the system unbootable if used in appropriately to reorder the boot sequence. I agree that more should be done to improve insserv, but the fact that one administrator didn't read the docs and tested an package in development in a way that broke his system should not lead to this package being removed from the archive. To debug, it would be useful to have the output from the 'insserv -v' (or just 'insserv -v -n' run), as well as the output from 'ls /etc/rsS.d /etc/rc2.d/' on the machines in question. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
