MSGID: <10jhd14$3993m$9@nntp.eternal-september.org> 26ce5e09   
   REPLY: <10jgba6$2sljl$1@nntp.eternal-september.org> e37693d4   
   PID: PyGate 1.5.2   
   TID: PyGate/Linux 1.5.2   
   CHRS: ASCII 1   
   TZUTC: 1100   
   REPLYADDR ldo@nz.invalid   
   REPLYTO 3:633/10 UUCP   
   On Mon, 5 Jan 2026 12:37:23 +0000, Daniel James wrote:   
      
   > On 04/01/2026 19:02, druck wrote:   
   >>   
   >> Also as someone else mentioned, it's actually predicable names   
   >> rather than unique names.   
   >   
   > Yes, for some strange value of "predictable" that requires you to   
   > know the naming scheme and also to know the hardware rather more   
   > intimately than most people usually have any need or desire to do.   
      
   I had a look on my system, to see where network interface names come   
   from. I found those names used inside /sys/class/net, which is   
   low-level information directly from the Linux kernel, not obtained   
   from udev rules or systemd or any other such userland source.   
      
   --- PyGate Linux v1.5.2   
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)   
   SEEN-BY: 105/81 106/201 128/187 129/14 305 153/7715 154/110 218/700   
   SEEN-BY: 226/30 227/114 229/110 112 134 200 206 275 300 317 400 426   
   SEEN-BY: 229/428 470 616 664 700 705 266/512 291/111 292/854 320/219   
   SEEN-BY: 322/757 342/200 396/45 460/58 633/10 280 414 418 420 422   
   SEEN-BY: 633/509 2744 712/848 770/1 902/26 2320/105 5020/400 5075/35   
   PATH: 633/10 280 229/426