<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">FYI:
<br>
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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The device naming for physical location in the system is separate from Network Manager itself and it requires the hardware to report the information. Personally
I like seeing the em# or p<slot#>p<port#> names because it helps me locate the NIC without having to run “ethtool –p”. One can use classic eth# names if preferred or if specific apps require it but so far I’ve not run across any that require the classic
names. In my view it is poorly written apps that insist on a specific naming convention that they don’t control rather than simply allowing one to specify the device name whatever it is. (In fact most apps shouldn’t even need the device name as they should
be relying on the IP or hostname setup rather than the device.) <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> ale-bounces@ale.org [mailto:ale-bounces@ale.org]
<b>On Behalf Of </b>Jim Kinney<br>
<b>Sent:</b> Tuesday, August 16, 2016 11:18 PM<br>
<b>To:</b> Atlanta User Group (E-mail)<br>
<b>Subject:</b> Re: [ale] OT: rant<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Bunch of different ways. NetworkManager can now handle all the magic script-fu to handle everything from simple dhcp through redundant teaming with failover.<o:p></o:p></p>
<p>But the output is still ifcfg-fu scripts in /etc/sysconfig/network-scripts<o:p></o:p></p>
<p>The article doesn't mention that 7 uses pci bus name stuff like enp0s0f1 instead of eth0.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Aug 16, 2016 6:03 PM, "Boris Borisov" <<a href="mailto:bugyatl@gmail.com">bugyatl@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Post in <a href="http://linuxtoday.org" target="_blank">
linuxtoday.org</a>:<br>
<br>
<span style="font-size:10.0pt">"How to configure a static IP address on CentOS 7 / RHEL 7"</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt">really? </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>