Comment 20 for bug 435935

This is a colossal mess. The bottom line seems to be that one has to recheck all service configs after an update, whether sysv or upstart. One also has to "know" which services have been "upstarted" in order to derive their expected behaviour.

Confidence in services' configs at reboot has just been reduced to near zero.

The current workaround, to retain confidence, seems to be to aptitude remove services to ensure they don't load. And that is bonkers!