Minimal install diff from F16 to F19 (TC6)

[Dan Williams]

On Fri, 2013-06-21 at 13:42 +0200, Florian Weimer wrote:
> On 06/20/2013 08:01 PM, Stephen Gallagher wrote:
> > Mind if I ask why you think this way about NetworkManager? The NM
> > currently shipping in Fedora 19 has full support for managing static
> > NICs, as well as bonding, bridging and VLAN support for enterprise
> > use-cases.
> >
> > NetworkManager has historically been perceived as a desktop/laptop
> > tool but in its current incarnation it should be usable for all but
> > the most esoteric enterprise workloads.
> 
> To clarify, this currently only applies to the GUI tool, right?
> 
> I recently hosed my desktop installation and couldn't bring up the VPN 
> from the command line, using nmcli.  The nmcli manual page suggests that 
> feature parity with the GUI tools is not a goal ("It is not meant as a 
> full replacement for nm‐applet or other similar clients but as a 
> complementary utility to those programs."), and the lack of actual 
> device configuration facilities in nmcli reflects that.  In Fedora 19, 
> the referenced nm-settings(5) manual page is missing, too.

We should change that.  Note that you *can* bring up VPN connections
from the command-line if all the secrets are already available (which
means stored in /etc/NetworkManager/system-connections).  It's the
editing UI (which is different for each VPN) and requesting secrets
(which is important for the RH VPN of course) which isn't implemented
for the CLI.  But we plan on doing this in the near future.

Dan

> Even if you end up configuring interfaces the old way under 
> /etc/sysconfig/networking-scripts, NetworkManager still offers the 
> benefit of the centralized configuration parsing.  But on the non-GUI 
> interface, functionality is either well-hidden or still missing.
> 
> -- 
> Florian Weimer / Red Hat Product Security Team