On Fri, Feb 14, 2014 at 8:23 PM, ToddAndMargo <[log in to unmask]> wrote:
> On 02/14/2014 04:59 PM, Nico Kadel-Garcia wrote:
>>
>> Beware The Dangling ifcfg-* Files of Doom
>>
>> Different network configuration tools, such as the old "netconfig"
>> tool, had bad habits of leaving various backed up or reference
>> templates for ifcfg-eth* files scattered throughout /etc/sysconfig.
>> They were nasty and confusing and tended to get reloaded, accidentally
>> based on phase of the moon and whether the chimps trying to code
>> NetworkManager had actually succeeded in writing Hamlet instead, and
>> gone off to get a banana.
>>
>> The "system-config-network" tool is not horrible, but leaves out a lot
>> of available options that need manual editing for more thorough
>> configuration. If you have to manually edit network settings for
>> stable servers, rip NetworkManager*out*  with the a prybar, if
>> necessary, and keep any running NetworkManager daemons from touching
>> your system.
>>
>> Historically, the /etc/sysconfig/network script is 'sourced' by the
>> various/etc/sysconfig/network-scripts/{if*} binary scripts, so it
>> should normally load from there if available. But coding standards can
>> change. Associating a gateway with a particular network port actually
>> has its uses if you have two ports on the same VLAN, and one port
>> *not*  to carry outgoing traffic.
>
>
> Hi Nico,
>
>     Network Manager seems to work okay in Fedora, but
> I do the same as you with SL
>
>     For SL, I have a special network configuration tool:  vi

Obligatory Emacs cartoon:

          http://xkcd.com/378/


> p.s. And stop calling them chimps!  Everyone know they are
> orangutans.  You'll hurt their feeling!  (Chimps are
> better looking.)

I feel much *safer* accusing chimps of being responsible for writing
NetowkManager than orangutangs.

    http://discworld.wikia.com/wiki/Horace_Worblehat