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
> (upstream isn't shipping it, at least not yet, and it's not in EPEL. Haven't
> check ELrepo or RPMforge yet.)  It allows full functionality in the CLI.

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


> But do realize that the following statement is in the upstream docs:
> "The Network Administration Tool is now deprecated and will be replaced
> by NetworkManager during the lifetime of ... 6." That means at some point
> it will be bye-bye system-config-network-tui. I hope they've gotten a
> text-mode nm-connection-editor by then.

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. 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. 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...