On 12/03/2012 07:12 PM, JA Magallón wrote:
To get the most 'pure' NM setup I could, I did this:
- disabled the ifcfg-rh plugin in NM.conf, just keyfile
- configured the network via nm-connection-editor, stored system wide
in /etc/NetworkManager/system-connections
- creaed a dummy ifcfg-eth0 file with
DEVICE=eth0
NM_CONTROLLED=yes
lines. No network info in there...just dummy file for initscripts to
ignore it,
as udev will be trying to create it with DHCP setup if not present...
Perhaps GUI toos and installer could do this also, if user wants the
interface
to be managed by NM. Perhaps it is time to deprecate ifcfg-rh and
create native
files for NM...
Yes, the problem at the moment is coordination between udev and
drakconnect and NM. The present policy is that NM will *not* be the
default, which is why udev creates the ifcfg files.
NM is designed to assume that it is in charge of all interfaces. The
only concession to coexistence with ifplugd is that if an ifcfg exists
*and* it has NM_CONTROLLED=NO, then NM will not try to control the
interface. Conversely, if ifplugd finds that an ifcfg exists *and* it
has NM_CONTROLLED=YES, then it will ignore it.
For total coordination between all of these, udev, drakconnect, and
ifplugd would have to look for and check /etc/NetworkManager.conf to
determine whether NM was active and whether it was paying any attention
to ifcfg files. That would determine whether ifplugd would attept to
control any interfaces at all, and whether drakconnect would even try to
build ifcfg files for them.
