Change semantics of S and K files

Presently, there are a lot of special cases:
- runlevel 0 and 6 unconditionally run "script stop" if they
  find a Kxxscript symlink. This may lead to trying to stop an
  already stopped device if for example switching to runlevel 0/6
  from runlevel 1. This can be fixed by stating the convention
  that it is the responsability of scripts to check that the service
  is running before killing it (or not running before starting it).
  Still, we shouldn't try to stop a service if it was marked K in
  the previous runlevel. And same for S files: we shouldn't try to
  start a service that was marked S in the previous runlevel. Note
  that changing runlevel is not a "reset": if a user has manually
  changed the state of a daemon, this state will remain the same
  upon changing runlevel if the S/K status of that dameon is
  the same in both runlevels.

- Sxxscript symlinks in runlevel 0/6 are run as "script stop"
  instead of the more intuitive "script start". This does not interact
  well with LSB-tools (some scripts would need "Default-Start: S 0 6"
  but then it is impossible to get correct "Required-Start" or
  "Should-Start" fields). Furthermore, having a counter-intuitive
  behavior is error prone. So now runlevel 0/6 will run "script
  sart" for a Sxxscript.

0 files changed, 0 insertions, 0 deletions