btw: Perhaps someone can explain me, when the Policy requests: >These scripts should not fail obscurely when the configuration files >remain but the package has been removed, as configuration files remain >on the system after the package has been removed. I mean are there any special technical reasons? At least from a conceptual point of view it should be just the opposite IMO. I see no harm if such a script would fail, except nasty error messages. And then a user can still decide to purge the package,.. and perhaps save his personal customisations to the scripts (if any). With dependency based boot it could even harm, that such scripts are there but don't fail. Imagine that another script requires or suggests it (either for start or stop) but the package is removed and the init scripts still gives an "everything ok exit 0". Cheers, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature