Great ! Let's Concretize the issue. I see the focus is on _whether the
behaviors of NetworkManager are just imperfect or confining user's choices _?
Before debating these questions should be answered (preferably by the authors
of NetworkManager):
Why is NetworkManager interfering with Dnsmasq?
What's the reason that NetworkManager provides few configuration
opportunities? Any difficulties?
Why should NetworkManager forcefully bundle a partial other software:
dnsmasq-base (at least at a first place) ?
If NetworkManager is the rival of Dnsmasq, then why does NetworkManager
contain a partial Dnsmasq? And hence, limiting Dnsmasq-base's configuration
ability. No one could configure such Dnsmasq-base. And further limiting the
full Dnsmasq (I just can't set self-defined DNS on my laptop via
dnsmasq-base)
No body found it weird?:-(
