Re: Bug#500176: This bug is still around and release-critical
Pierre Habouzit <firstname.lastname@example.org> wrote:
> I believe the problem here is somehow very generic, and that using a
> virtual package like proposed in the bug report (#500176) doesn't scale
> well. Especially for dns daemons. Packaging two of them myself (nsd3
> that is an authoritative server only, and pdnsd that is a caching daemon
> only) I can tell the virtual package solution would be a mess: I _want_
> to be able to use nsd3 _and_ pdnsd on the same machine (I actually do
> since the former binds to the external IPs only and pdnsd to 127.0.0.1)
> Anyways I think there is a more general solution to find and here are a
> path. The fact that Debian starts every single service on first install
> is something that we strive for, but causes some grief for sysadmins
> that don't wish to open an unprotected service before they configured
> it. It also generates the issue we're disussing.
If the idea of update-rc.d disable|reenable gets implemented, it would
be enough to disable a service after first installation. update-rc.d
could do that.
Die NASA brauchte 12 Jahre um einen Kugelschreiber zu entwickeln, der
kopfüber, in der Schwerelosigkeit und unter Wasser schreiben kann.
Die Russen benutzten einfach einen Bleistift …