On Wed, 8 Mar 2006, Henrique de Moraes Holschuh wrote:
Forwarding to the mailing list for the SysvInit maintainers (contacting me directly isn't nearly as effective, I am not even the most active of the sysvinit maintainers... ;-) ).
Yesterday I found out that [EMAIL PROTECTED] is really the right place to report the problem to. I reassigned the bug to initscripts and you can the reasons here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=359137;msg=17 I went even further and found out that the issue for the problem that bothers me now on four (= all my testing boxes) boxes and is reproducible occured when changing from initscripts_2.86.ds1-10_i386.deb to initscripts_2.86.ds1-11_i386.deb . So it would be great if a more educated person than me could look into the changes between these two versions. I would be happy to provide any needed information, but I have no clue what information might help here. So please ask me the right questions what might be helpful. My fallback plan is to stupidly revert the changes and reboot my box. If it is working again whe found the problem but I would prefer a more clever method than trial and error. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]