Bob Proulx <b...@proulx.com> writes: > No. That is too late. By the time you are disabling something it has > already been installed and started in postinst scripts. Using > policy-rc.d is the only way to prevent unknown anythings from being > enabled before installing.
Ah, yes, that's true. > P.S. Related to this is that I really think that if you want a daemon > running and install it and the package can configure it and start it > then it should do so. If you don't want something running then don't > install it. Or remove/purge it. I am not advocating any change that > would get in the way of making an installation not start a daemon that > it can do so. The chroot case really is a special case. Yes, the general Debian practice is to assume that, if you install a daemon, you want the daemon running. If that's not the case and you don't want it to start even temporarily, you're correct that policy.d is the only mechanism to achieve that. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87k32rhwp2....@hope.eyrie.org
