On Wednesday, June 08, 2011 07:36:35 PM you wrote:
> On Wed, Jun 8, 2011 at 10:54 AM, Lamar Owen <[log in to unmask]> wrote: 
> > That I'll agree with; thus the cnetworkmanager package wishful thinking

> What does cnetworkmanager add to nmcli? Looking at the nmcli man page,
> it looks like it allows you completely to manage a NIC.

I think cnetworkmanager allows an easier 'one-liner' especially for wireless connections.  I don't see options to create or configure connections of other kinds.  Would be great to have those options, maybe even with a curses (or similar) interface.  It's a start, but it's not a full replacement for the GUI nm-connection-editor yet.

> And it'll happen because, as I saw on a fedora-devel thread, upstream
> doesn't want to have to put in the resources to maintain two methods
> of managing NICs. Once NM can manage bonding, bridging, vlans, etc,
> system-config-* will be deprecated. 

A reasonable goal; maintaining any package requires time and manpower, and both of those cost something at some level.  

> In another thread, Nico'd said
> that NM's crap for various reasons (harsh and possibly true) but we'll
> eventually have to deal with NM even on headless boxes. 

Yep.  And feedback of this nature (how to deal with it, and what options need to go upstream of upstream) is needed.  Whether it will be heeded or not..... well, that's actually a political issue, and depends a great deal on which developers are involved.

> We just have
> to go with the flow in the same way that Debian and Ubuntu have
> adopted grub2 without it bringing *that* much more to the table than
> grub1 - and, even though Fedora and TUV seem to be dragging their feet
> in respect of grub2, it's a pretty safe bet that it'll be the default
> for SL7 and we'll have to make do with it too. It's called progress...