[ale] OT: rant

[DJ-Pfulio]

I purge NM from all systems. It used to be confused by non-trivial network
setups and just got in the way. That habit has served me well for years.

If I need wifi connections while away from home, using wicd-curses is much
easier than fighting with NM. IMHO.

Mot really interested in using a full GUI for this stuff. Why learn that when I
won't work on servers?

On 08/17/2016 10:48 AM, Lightner, Jeffrey wrote:
> Yep - like I said for later RHEL6.x & all of RHEL7.x Network Manager works
> fine.     I first used it on early RHEL6.x and the recommendation from RedHat
> back then was to turn it off.
> 
> 
> -----Original Message----- From: Derek Atkins [mailto:warlord at MIT.EDU] Sent:
> Wednesday, August 17, 2016 10:32 AM To: Lightner, Jeffrey Cc: Atlanta Linux
> Enthusiasts Subject: Re: [ale] OT: rant
> 
> "Lightner, Jeffrey" <JLightner at dsservices.com> writes:
> 
>> FYI: Network Manager didn’t come about until RHEL6 and early advice was to
>> turn it off.   On later RHEL6.x versions and RHEL7 it is not quite the
>> problem it was in early 6.x.
>> 
>> The odd thing about it is that even when you’re not doing DHCP it wants to
>> set your /etc/resolv.conf based on entries stored in your /etc/sysconfig/
>> network-scripts ifcfg-* files.
>> 
>> Another thing that bit me early on when I tried to use it was that it 
>> stores aliases such as eth1:1 in the main ifcfg-eth1 rather than in
>> separate ifcfg-eth1:1 as the older network tool did.   When you’d start
>> networking it would find your ifcfg-eth1:1 but assume you meant that to be
>> eth2.   D’oh!
> 
> This has certainly been fixed.  Current NM properly uses ifcfg-eth1:1,
> provided you also have an ifcfg-eth1 file.
> 
> -derek
>