Updating 3-months old system.
What should I watch for when it comes to updating from eudev to udev
from the news file:
"If you DO NOT want the "predictable interface naming" of newer versions
of udev and instead prefer the old style (e.g. "eth0"), there are several options available."
my interface is: enp4s0
so I assume it will become: eth0 after upgrade, changing the name via "rc-update" will be necessary.
Updating 3-months old system.
What should I watch for when it comes to updating from eudev to udev
from the news file:
"If you DO NOT want the "predictable interface naming" of newer versions
of udev and instead prefer the old style (e.g. "eth0"), there are several options available."
my interface is: enp4s0
so I assume it will become: eth0 after upgrade, changing the name via "rc-update" will be necessary.
Is there any official guide to it?
--
Thelma
thelma@sys-concept.com wrote:
Updating 3-months old system.
What should I watch for when it comes to updating from eudev to udev
from the news file:
"If you DO NOT want the "predictable interface naming" of newer versions
of udev and instead prefer the old style (e.g. "eth0"), there are several
options available."
my interface is: enp4s0
so I assume it will become: eth0 after upgrade, changing the name via "rc-update" will be necessary.
Is there any official guide to it?
--
Thelma
If I recall correctly, the enp* names are the new names. Unless you
tell it to use the old style, eth0, eth1 etc, the new names will be
used. If that is what you want, it should be as simple as unmerging
eudev and emerging udev. I might add, you may want to reboot especially
if you use the old naming method. The kernel assigns the names during
boot up. Restarting udev wasn't quite enough when I switched.
If you look for my previous thread on this, there is more info there.
Hope that helps.
Dale
:-) :-)
I used the old naming method with eudev. When I switched, the names of
the networks changed. When I rebooted, no network because they were not named correctly for the files I had. It had been so long, I forgot how
to get the names or what to do to get the right files. If I had either
been ready for the new names or had already been using the new names
before the switch, it would have been no trouble at all. Since you are using the new naming method already, you should have no problem. It *should* just work.
Let's hope it works that way. :-D
Dale
:-) :-)
On 12/19/21 9:48 AM, Dale wrote:
thelma@sys-concept.com wrote:Thanks for explanation, seems like it is nothing to worry.
Updating 3-months old system.
What should I watch for when it comes to updating from eudev to udev
from the news file:
"If you DO NOT want the "predictable interface naming" of newer versions >>> of udev and instead prefer the old style (e.g. "eth0"), there are several >>> options available."
my interface is: enp4s0
so I assume it will become: eth0 after upgrade, changing the name via "rc-update" will be necessary.
Is there any official guide to it?
--
Thelma
If I recall correctly, the enp* names are the new names. Unless you
tell it to use the old style, eth0, eth1 etc, the new names will be
used. If that is what you want, it should be as simple as unmerging
eudev and emerging udev. I might add, you may want to reboot especially
if you use the old naming method. The kernel assigns the names during
boot up. Restarting udev wasn't quite enough when I switched.
If you look for my previous thread on this, there is more info there.
Hope that helps.
Dale
:-) :-)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 285 |
Nodes: | 16 (2 / 14) |
Uptime: | 71:42:50 |
Calls: | 6,488 |
Calls today: | 1 |
Files: | 12,096 |
Messages: | 5,275,722 |