Lamar Owen writes:
> I'm assuming you filed a bugzilla upstream?  Also, in your ifcfg-ethX
> files you have the ability (that is fully documented in upstream's
> documentation) to tell NM to not manage a particular interface, but
> just pull it up.  It's just a matter of learning a newer way of doing
> things.

The big problem with this is that even if you do this, NM returns "ok"
to the startup sequence well before it actually gets around to bringing
up your network(*) - then things like autofs and nis fall over.  I
actually did file a bug back when this behavior hit Fedora 11 (remember,
Fedora is TUV's beta cycle) and got no love (although a cleaner
workaround than mine was presented):

  https://bugzilla.redhat.com/show_bug.cgi?id=506533

But, since this bug seems to have survived the development cycle I'm
happy to reopen this particular against 6.  However, I've no desire to
reintroduce NM on any of my machines to verify it so would want to turn
the bug over to someone who does want to fight the fight, and it also
should be checked that it's still a problem in 6.1.

       Alec

(*) - obviously not for everyone if yours works, but relying on a
hardware-dependant race condition isn't a very robust solution.

-- 
 	    Alec Habig, University of Minnesota Duluth Physics Dept.
	    		    [log in to unmask]
		       http://neutrino.d.umn.edu/~habig/