eth0 again

[Amadeus W.M.]

On Sun, 20 Jul 2014 19:50:44 -0500, Thomas Cameron wrote:

> On 07/20/2014 03:30 PM, JD wrote:
>> On Sun, Jul 20, 2014 at 1:49 PM, Thomas Cameron
>> <thomas.cameron at camerontech.com
>> <mailto:thomas.cameron at camerontech.com>>
>> wrote:
>> 
>> 
>>     If you disable NM, you need to enable network. From a local console
>>     (in other words, don't do this over a network session like ssh):
>> 
>>     systemctl disable NetworkManager.service systemctl stop
>>     NetworkManager.service systemctl enable network systemctl start
>>     network
>> 
>>     Thomas
>> 
>> 
>> D
>> ​oesn't this prevent you from connecting to open hotspots?
>> ​ ​The ​ nm-applet ​ will not be able to communicate with NM and thus
>> will not be able to list detected ssid's.​
> 
> Fair point.
> 
> So disable NM for the eth0 interface only and turn on the network
> service.
> 
> Change NM_CONTROLLED=yes to NM_CONTROLLED=no in the ifcfg-eth0 file.
> Then NM will stop managing that interface, but still manage the wifi
> interface.
> 
> Thomas

Yes, I remember now, that's how you tell NM to leave your network card 
alone. Regardless, though, I disabled NM alltogether and enabled and 
started network.service so now the card is no longer under NM and I have 
network. However, the device is still named em1.