Description of problem: When I install nss-mdns, it automatically adds itself to /etc/resolv.conf. Version-Release number of selected component (if applicable): 0.10-3.fc8 How reproducible: Always Steps to Reproduce: 1. Install the package. 2. grep ^hosts: /etc/nsswitch.conf Actual results: hosts: files mdns4_minimal [NOTFOUND=return] dns Expected results: What I had there before.
Hmm? Where's the bug? Don't install nss-mdns if you don't want to use it!
The bug is that this is inconsistent with how every other nsswitch module is packaged. Having the bits installed on the disk does not automatically imply that they're expected to be used.
Uh? I mean, we also activate Samba by default when it is installed, don't we? Just because other nss modules don't enable themselves when installed this shouldn't be a reason for nss-mdns to not do it. nss-mdns is about zeroconf, and thus you shouldn't really need to configure it yourself. It should just work. If other nss modules don't activate themselves by default when they are installed then I would say it is a bug in those packages, -- unless of course they need some very specific configuration before they can be enabled. I really see no reason why this behaviour of the nss-mdns package should be considered a bug.