Conversation

Notices

1. :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Thursday, 14-Mar-2024 22:53:49 JST :apa: スプリットショックウイルス †

   They're just making shit up at this point.

   • † top dog :pedomustdie: likes this.
   • m0xEE (m0xee@breloma.m0xee.net)'s status on Friday, 15-Mar-2024 02:57:17 JST m0xEE

     in reply to

     • Phantasm
     @splitshockvirus
     Gimme-gimme-gimme!
     I have a great quote just for this occasion: https://fluffytail.org/objects/76032c01-373e-461b-acbb-08d1237088c5
     Or on my instance as FluffyTail doesn't show shit to unauthenticated users: https://breloma.m0xee.net/notice/AfiTuyvtkA4sbDUYBE
     
     What systemd (its udev part in particular) has given us are (very straightforward and) "predictable hardware based identifiers for ethernet and WiFi devices" (instead of such confusing shit as eth0 and wlan0) :marseyemojirofl:
     And it might seem that it only happens in some complex configurations, when multiple adapters are used, but here's the id of the built-in network card in my PowerMac G5: enP1p4s15f0 — I swear, when I have to use this somewhere, I can't even remember it, I have to either copy it or write it down. But okay, however old it might be, it's still an SMP-capable dual CPU workstation and theoretically it can have very complex configuration and when this hardware was in its prime I might've wanted to have more network cards in it.
     You know what the identifier of the sole wired network interface in the Mac Mini this instance runs on is — and it isn't theoretical this time, this thing will never have more of them unless they are virtual? It is enP2p0s15f0
     Pretty neat, huh? Brilliant solution for the problem that in absolute most cases have never existed :marseysmug2:
     
     @phnt , I feel bad for making fun of your point behind your back so I'll just CC you here.
     † top dog :pedomustdie: likes this.