device names are all kernel and udev. nothing to do with network manager.
if you want to get predictable interface names, set up udev rules
appropriately.
https://www.kernel.org/pub/linux/utils/kernel/hotplug/udev/udev.html
___
CentOS mailing list
Cen
On 5/19/2015 12:54 PM, m.r...@5-cent.us wrote:
> Excerpt I *still* see absolutely no use in an enterprise environment, where
> we're *all* wired, even the laptops when folks bring them in. This improves
> throughput and security, of course.
>> Great post. I am just in the process of building my fir
Kirk Bocek wrote:
> On 5/19/2015 10:54 AM, m.r...@5-cent.us wrote:
>> And that one drives me nuts. It breaks PXE boot kickstart builds. Maybe
>> *you* have all same model systems from the same manufacturer; we've got
>> boxen from... at least five or six manufacturers, of varying
>> ages, from the
On 5/19/2015 10:54 AM, m.r...@5-cent.us wrote:
And that one drives me nuts. It breaks PXE boot kickstart builds. Maybe
*you* have all same model systems from the same manufacturer; we've got
boxen from... at least five or six manufacturers, of varying
ages, from the 10+ yr old Altix 3000 from S
Kirk Bocek wrote:
> On 5/19/2015 10:24 AM, James Hogarth wrote:
>> On 19 May 2015 11:40, wrote:
>>> Or if you want a bigger hammer:
>>>
>>> systemctl disable NetworkManager.service
>>> systemctl enable network.service
>>> systemctl stop NetworkManager.service
>>> systemctl start network.service
On 5/19/2015 10:24 AM, James Hogarth wrote:
On 19 May 2015 11:40, wrote:
Or if you want a bigger hammer:
systemctl disable NetworkManager.service
systemctl enable network.service
systemctl stop NetworkManager.service
systemctl start network.service
The above will disable NetworkMangler an
On 19 May 2015 11:40, wrote:
>
>
>
> Or if you want a bigger hammer:
>
> systemctl disable NetworkManager.service
> systemctl enable network.service
> systemctl stop NetworkManager.service
> systemctl start network.service
>
> The above will disable NetworkMangler and return control of the network
On Mon, 18 May 2015, James Hogarth wrote:
On 18 May 2015 at 20:10, wrote:
Someone else got the 7 pxe install going, and one thing that's annoying is
that NetworkMangler appears to be regularly trying to fire up the wifi.
On a workstation, in a wired environment. I just want to tell NM to kno
James Hogarth wrote:
> On 18 May 2015 at 20:10, wrote:
>> Someone else got the 7 pxe install going, and one thing that's annoying
>> is that NetworkMangler appears to be regularly trying to fire up the wifi.
>>
>> On a workstation, in a wired environment. I just want to tell NM to
>> knock it off
On 18 May 2015 at 20:10, wrote:
> Someone else got the 7 pxe install going, and one thing that's annoying is
> that NetworkMangler appears to be regularly trying to fire up the wifi.
>
> On a workstation, in a wired environment. I just want to tell NM to knock
> it offIt's Monday, and my sear
Someone else got the 7 pxe install going, and one thing that's annoying is
that NetworkMangler appears to be regularly trying to fire up the wifi.
On a workstation, in a wired environment. I just want to tell NM to knock
it offIt's Monday, and my searching isn't going too well. Clues for
the p
11 matches
Mail list logo
