@nixCraft@mastodon.social
Who misses the old Linux Ethernet names? Remember when your network interfaces were just eth0 and eth1? Now we have long names like enp0s25. Let's see where you stand.
Who misses the old Linux Ethernet names? Remember when your network interfaces were just eth0 and eth1? Now we have long names like enp0s25. Let's see where you stand.
@nixCraft@mastodon.social I always start looking for eth0, then remember itβs gone for whatever reasons and fuck around to find the new name which my brain then instantly forgets again.
@nixCraft@mastodon.social I'm a multi-decade user of Unix, BSD, and Linux which means I'm nostalgic for ethX naming, but at the same time I understand the need for deterministic naming of interfaces (Checkpoint firewall admins know /exactly/ what I'm talking about - there's a kb that talks you through pinning this MAC to that interface name).
So I'm conflicted. I prefer the old naming standard, but appreciate the new way means that interfaces don't "move around".
Not a fan of Linux distributions getting rid of ifconfig/arp/netstat though.
@nixCraft@mastodon.social There's a boot parameter you can put in your bootloader that replaces those long names with the older names. I use this boot parameter.
The parameter in question is "net.ifnames=0". If you're using GRUB, put it under "GRUB_CMDLINE_LINUX".
@nixCraft@mastodon.social My question is, why do we have those overcomplicated names for ethernet interfaces?
@nixCraft@mastodon.social I miss it, but the new names are better.
@odysseywestra@linuxrocks.online @nixCraft@mastodon.social I believe it was so they were deterministic based on bus/slot location . Plugging in a new device could have reordered eth0,eth1. But the new naming βfixedβ that.
@odysseywestra@linuxrocks.online @nixCraft@mastodon.social I believe it was so they were deterministic based on bus/slot location . Plugging in a new device could have reordered eth0,eth1. But the new naming βfixedβ that.