> On 09/02/2020 23:55, Nicolas Kovacs wrote:
>
> Hi Nicolas,
>
> [snip]
>
>> Maybe there's a reason to make NetworkManager more or less mandatory
>> from now on, but I don't see it. So I thought I'd rather ask on this
>> list.
>
> Like you, I read about NetworkManager becoming the default tool for
Le 10/02/2020 à 16:12, Leroy Tennison a écrit :
There may be ways to force NIC naming, I've done so but only on Ubuntu so
you'll need to do the research if it's important to you. Things to look for
based on my experience: 70-persistent-net.rules, net.ifnames=0,
biosdevname=0.
That's exactly
On Mon, Feb 10, 2020 at 03:12:11PM +, Leroy Tennison wrote:
> There may be ways to force NIC naming, I've done so but only on Ubuntu so
> you'll need to do the research if it's important to you. Things to look for
> based on my experience: 70-persistent-net.rules, net.ifnames=0,
On 09/02/2020 23:55, Nicolas Kovacs wrote:
Hi Nicolas,
[snip]
> Maybe there's a reason to make NetworkManager more or less mandatory
> from now on, but I don't see it. So I thought I'd rather ask on this list.
Like you, I read about NetworkManager becoming the default tool for
CentOS 8. So I
Since you asked, the circumstance warranting registry editing is cloning a
running system to create a new instance for a different purpose while bringing
it up on the same subnet. Yes, it's a little messy but it works. And thanks
for the pointer about virt-sysprep.
There may be ways to force NIC naming, I've done so but only on Ubuntu so
you'll need to do the research if it's important to you. Things to look for
based on my experience: 70-persistent-net.rules, net.ifnames=0, biosdevname=0.
From: CentOS on behalf of
Once upon a time, Stephen John Smoogen said:
> The reason is that having 1 way to configure networks makes it so the
> developer and tech support only have to diagnose issues from 1 set of tools
> versus two different ones (and occasionally 2 competing ones if both are
> trying to do their job at
On Mon, 10 Feb 2020 at 02:55, Nicolas Kovacs wrote:
> Hi,
>
> I'm currently reading the upstream "Considerations in adopting RHEL 8"
> document. The chapter about networking states that traditional networking
> scripts (shipped with the network-scripts package) are considered obsolete.
>
> I
8 matches
Mail list logo
