Network Manager dependencies

Clint Byrum clint at
Wed Aug 22 20:13:13 UTC 2012

Excerpts from Tom H's message of 2012-08-22 00:24:11 -0700:
> IMO, we'll end up sooner or later using NM on X-less boxes by default

I do not share your opinion. While I'm not ifupdown's biggest fan, it
will likely be the network configuration tool of choice on servers for
the forseeable future. NM is specifically targetted at the more flexible
networking requirements of laptops and mobile systems. It does not,
however, take into account all of the myriad use cases for servers that
ifupdown handles.

> NM on Fedora can now handle bonding and bridging by reading
> "/etc/sysconfig/netwok-scripts/ifcfg-*" files.
> The following NEW packages will be installed:
> consolekit dconf-gsettings-backend dconf-service dnsmasq-base
> glib-networking glib-networking-common glib-networking-services
> gsettings-desktop-schemas iputils-arping libck-connector0 libdconf1
> libgudev-1.0-0 libnetfilter-conntrack3 libnl-route-3-200 libnm-glib4
> libnm-util2 libnspr4 libnss3 libpcsclite1 libpolkit-agent-1-0
> libpolkit-backend-1-0 libproxy1 libsoup2.4-1 libsysfs2 libxml2
> network-manager policykit-1 wpasupplicant

Thats cool. If we go down that route in Ubuntu, perhaps then we would
address the dependencies that you mentioned. But AFAIK, there is no such
plan and ifupdown is safe for the time being.

More information about the Ubuntu-devel-discuss mailing list