On 7/15/24 6:29 AM, Tim via users wrote:
On Mon, 2024-07-15 at 10:09 +0100, Barry wrote:
The reason for the renaming is to ensure that the interface names are
consistent in every boot. It is an issue on some systems that an
interface may be eth0 on one boot the eth1 on the next.
Consider using the new naming so you have stability.
FYI it’s been this way for many years, not sure why this
was not the case in f38 for you.
Though, for many people it's solving a problem that they don't have.
I can remember eth0 if I'm having to fix up a system on the command
line, I cannot remember the oddball thing the system named it, EVER
(enp0s31f6).
For me, and probably everyone else, the solution would have been for
some unique part of the hardware (such as MAC, or PCI slot data, etc),
to get tied to eth0 during installation. Likewise for eth1, etc.
Rather than used to create a gibberish name for it.
The kernel doesn't have access to that configuration. That's why you
need to configure the names you want in NetworkManager.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
