On Sun, Mar 08, 2009 at 03:19:09PM +0100, Pierre Habouzit wrote: > Oh boy, you absolutely don't get it.
of course I do, > I give the two most used configurations for free yes, and while it's perfectly OK regarding your intentions, the manner in which it's implemented isn't. > If you're not in those cases that probably match > 95% of the pdnsd uses cases, then you chose > "Manual" during the install and you're done. Well, I _am_ in those 95%, because I do need my pdnsd configuration to be updated dynamically by resolvconf, yet I have small site-specific needs like the mentioned server_ip setting for qemu/kvm guests. And I'd appreciate ability to make the changes with minimal effort, and then to have them preserved on site. > Again the debconf templates _TELLS YOU_ to chose > Manual when you have to change server_ip. Nope, you're wrong (pdnsd.templates from stable): > Note: If you already use a DNS server that listens to 127.0.0.1:53, > you have to choose "Manual". So the only phrase related to IP address is not about server_ip at all. > > four configuration files: > > * /etc/default/pdnsd > > * /etc/pdnsd.conf > > * /usr/share/pdnsd/pdnsd-recurse.conf > > * /usr/share/pdnsd/pdnsd-resolvconf.conf > > instead of just one is very confusing. > > No there are two configuration files: > * /etc/default/pdnsd > * /etc/pdnsd.conf It's just a matter of advocacy - if you assume placement under /usr/share subtree to be a defining characteristic, then /usr/share/pdnsd/pdnsd-*.conf are not configuration files. If instead you assume syntax, semantics and effect of them on pdnsd's behaviour, then they are. > /etc/pdnsd.conf is the default configuration file. > > When you're lucky enough so that the two > possible builtin configuration I did suit your > needs, debconf allow you to simplify that work > and do all by itself, touching only > /etc/default/pdnsd. As I've said earlier, it's OK with me to choose "resolvconf" mode. Yet I'd be grateful to pdnsd to allow me (1) to choose a mode, (2) make small modifications to its behaviour and (3) to keep them across upgrades. I think, if you opted to _generate_ /etc/pdnsd.conf from one of the resolvconf/resurse templates (depending on debconf parameter), this would fit the (1)-(2)-(3) scenario. Current solution is dead inflexible though... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
