reopen 353311 thanks, On Fri, Mar 03, 2006 at 01:23:44PM +1100, Anand Kumria wrote: > Actually libnss-mdns has to recommend zeroconf. > > How else do you expect the entire zeroconf stack to work when two > machines only has a cable between them? > > The zeroconf stack is supposed to work without a DHCP present on the > local LAN segment, only with this recommendation does that.
Rigth you zeroconf stack has to work, so the zeroconf package has to recommend
on libnss-mdns.
> It isn't a hard dependancy only because there might be some obscure
> reason not to have the zeroconf stack working when there is no DHCP
> server.
You need to look at this from the other side. If you have zeroconf you indeed
really want mdns. But in case one install mdns, that doesn't mean you want
zeroconf in any way.
I personally use mdns on a various machines without zeroconf, why? So i can
have normal programs resolve .local names. This is very usefull in combination
with things like avahi, which can discover services on .local machines. And
even more on networks where i don't get a static ip, i can always find my
laptop by going to spring.local (which rocks imho).
To make matters worse, most package management programs install recommends by
default and zeroconf has various longstanding bugs of people saying that it
screws up there network(ing). So that alone is enough reason to not recommend
it unless it's absolutely necessary.
To summarize, nss-mdns is very usefull without zeroconf, zeroconf is not
very usefull (normally) without nss-mdns. Imho this can only lead to the
conclusion that zeroconf needs to recommend nss-mdns, but nss-mdns shouldn't
recommend zeroconf.
Sjoerd
--
FORTUNE'S RULES TO LIVE BY: #2
Never goose a wolverine.
signature.asc
Description: Digital signature
