Re: install_initd behavior for non-LSB init scripts.

This makes absolutely no sense.  What if the script 
has nothing to do with the scripts immediatly before
and after it?  

S80 is far better than S01 (before the network
interface even comes up), regardless of what is 
immediately before or after S80.  

Also, a collection of third-party services could 
at least be in the proper order within themselves.  

S50acme-a, S51acme-b, S52acme-c, etc.  

Maybe these services need to start in this order, 
but don't care what other things come before or after
them.  SuSE's install_initd could potentially set one 
or all of these to S01 and break the acme suite. 

You never answered my questions.  

1. Why S01...  ?  What do you gain from moving
it here?  

2. What harm is done by leaving it where it is?  

Please, I beg of you, fix this broken behavior. 

>>> Thorsten Kukuk <[email protected]> 10/17/03 12:32 AM >>>

The script will only be moved, if the script before and/or
after this script will be  renumberd. If the scripts before and
after this script will be renumberd, your selected fix
number is wrong and it doesn't matter where it will be moved
too, it is always wrong.