Systemd predictable network interface names are awesome.
Not only I get easy to remember names like enp2s0f0u7u3c2 but I _also_ get to experience a machine not coming back up after reboot because a new (non-NIC!) PCIe card caused existing names to shuffle around.
@q3k yea we're predictable
predictably bad
@q3k real talk: I feel like a system like /dev/disk/by-* for interface names would solve many of these problems: it allows you to be specific when you need to, and to be generic when you don't
there's probably a way to do this with interface aliases, thinking of it 🤔
@q3k Here's another fun thing:
Power machines can have differen PCIe busses, so you can actually get things like
`enP19p96s0f0`, and if your driver decides, even `enP19p96s0f0np0` .
IF you then want a VLAN on that, the canonical name would be something like
`enP19p96s0f0np0.1450`. Thats 20 characters. Interface names *can only* be 16 (in practice 15) characters long.
Fun esues.
OMG don’t bring back the PTSD about name length restrictions. cm-usb3-a-gige (strlen = 14) u-dev rule works fine, ms-usb3-a-dongle (strlen = 16) => ‼️🚨🚫 I finally find in logs (networkctl info or status IIRC) a cryptic error from networkd where the only Google result is the error in the systemd repo. 🤦♂️ At least once I got that far it took about 15 minutes to realize my folly but they really need to plumb the error reason up to the log message output point!
@q3k I really like #OpenBSD's approach. Usually, you configure network interfaces in a file called /etc/hostname.<if> where <if> is the name of the interface.
To avoid the renaming problem, you can also name the file /etc/hostname.XX:XX:XX:XX:XX:XX so it's bound to the MAC address.
More details in https://man.openbsd.org/hostname.if
q3k 
jn (big endian energy)
Wolf480pl
Mango
qwertyoruiopz
Manawyrm | Sarah
Jesus Michał "Le Sigh" 🏔 (he)
Shiz
Tobias
Jevin Sweval
uis
Niels Moseley
Matthias Schmidt
Andrew Hewus Fresh
Florian
mx alex tax1a - 2020 (6)
rreignier
🇺🇦 haxadecimal 🚫👑
AN/CRM-114
Cosmin