Alt account of @Badabinski

Just a sweaty nerd interested in software, home automation, emotional issues, and polite discourse about all of the above.

  • 0 Posts
  • 7 Comments
Joined 24 days ago
cake
Cake day: June 9th, 2024

help-circle
  • Eh, I have a low tolerance for this kind of bullshit. I know what I like and what I don’t like. I went through their posting history before blocking them, and I found that the subjective quality of their contributions failed to outweigh my irritation towards them. To me, it’s better to just block them and never risk seeing comments like this from them again. There are a bunch of people on this site who I’d rather interact with.

    As a bonus, they’ll only ever have one shitty passive aggressive comment from me to deal with.




  • I always just derive the interface name from first principles. Like, if I want to know which interface will be used to get out to the internet in a script, I’ll just find the one that’s L2 adjacent with the default gateway. If I’m given an egress or cidr, I’ll just find the interface that has that IP. Modern iproute2 has a JSON output option which makes getting this information pretty trivial. Doing that means that it doesn’t matter what scheme your OS is using.

    I personally prefer the persistent names for Ethernet, although I don’t like them for WiFi. Luckily, it seems like my wireless adapter always just ends up as wlan0. I’m not sure why that’s the case, but it works out well in the end for me.