NetworkManager ( & bind)

[Chris Adams]

Once upon a time, Dan Williams <dcbw at redhat.com> said:
> On Wed, 2005-01-12 at 23:25 -0600, Satish Balay wrote:
> > Any idea why NetworkManager requires bind?
> 
> It uses bind in a caching-nameserver functionality and named should
> _not_ be turned on my default in this configuration.

This new requirement broke my local named config.  I had bind installed
but not caching-nameserver; installing caching-nameserver (to fulfill
the dependency) moved my named.conf to named.conf.rpmsave and yum didn't
even tell me about it.

NetworkManager's RPM says "It is intended only for the desktop use-case,
and is not intended for usage on servers.", yet it is installed by
default in the "Base" group (which means going forward bind and
caching-nameserver will also be installed by default).  I don't need
this if I'm building a firewall or server (it actually gets in the way
of configuring bind).

It seems that too many things are creeping into Base; what makes
"cyrus-sasl-plain" or "mt-st" or "slocate" mandatory?  Why are Bluetooth
utils and "numactl" included in Base by default?

-- 
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.