there is a valid reason for this which most linuxlarpers won't understand

@stackallocator vagueposting...

@stackallocator Used to be so annoying when eth1 switched to eth0 following a reboot.

@stackallocator "valid" doesn't mean "not annoying AF" 😀

@stackallocator just because there's a valid reason doesn't mean it isn't grating whilst you try to fix your broken networking

@stackallocator Okay, but hear me out here, I fucking hate it.

@stackallocator SystemD is not a valid reason, it's a mental illness.

@stackallocator Except that they aren't actually predictable in many cases and end up relying on the hardware mac. So if you have configuration that depends on a specific physical interface, you might as well match it by mac anyway.

@stackallocator For those unaware, the OS assigns eth0 to the first network device loaded at boot, eth1 to the 2nd, etc. Problem being that WHICH device is eth0 and eth1 changes because it's a race condition. So instead it hardcodes the address to each.

@stackallocator Think it's to give consistent names to the ethernet ports even when you add/remove some, which can happen alot if you're using USB ethernet adapters and such

@stackallocator Always love linux networking. Changed an option on CLI? No the fuck you didn't, because that was one of the dozen network managers that exist for some reason but isn't active.

@stackallocator There is a valid reason. Though, if you only have a single motherboard ethernet port to contend with you probably won't really have much appreciation or patience for that reason, because it's not very relevant to your situation.

@stackallocator Oh I know why, doesn't mean it can't be annoying. And SysV Init for Life, systemd sucks.... d

@stackallocator So called "predictable" interface names changing when I add a GPU.

@stackallocator Been using Linux for about 20 years and I don't know the reason for the complex interface names What a fucking larper I am

@stackallocator why? mine running debian trixie and my ethernet is en01, can't see any reason to make is as long as hard drive UUID can go

@stackallocator The valid reason is interface naming consistency which was achieved in the old naming scheme as well, by udev persistence scripts,. Fortunately one can still choose between naming patterns.

@stackallocator yep yep, now interface names are PREDICTABLE. Not that you can predict them in any given system and all scripts are failing due to it, but its for greater good.

@stackallocator Flags in bio. Opinion ignored.

@stackallocator every bad decision was based on seemingly valid reasons

@stackallocator Yeah, love my GPU crashing and failing to come back being the reason my server doesn't come back onto the network properly after a reboot... I've had a similar number of problems with both methods.

@stackallocator Hot take: BSDs do a better job about this with having distinct driver ifnet names for a specific family of hardware. (However, this does have downsides, namely due to the same unstable ordering bug mentioned earlier, but it’s less likely since there’s multiple namespaces.)

@stackallocator FUCK SYSTEMD

@stackallocator all in all their implementation of this makes sense, and they’re nice enough to give you the option to opt out of it it’s makes sense to have it. I don’t think they could of done that any better really

@stackallocator Of course systemd would end up calling name mangling "valid". How does manufacturer and physical slot make it useful? The only sane way is to map a human-defined name to MAC address.

@stackallocator #Why_this_one_was_abandoned" target="_blank" rel="nofollow noopener">wiki.debian.org/NetworkInterfa…

@stackallocator Ain't that predictable if you got multiple same NIC

@stackallocator oh i'm sure your massive effing brain knows why! i'm sure a;lksejndfiko;ae9p845hrqae3p9u4fhoupsazerfnbosui;'djnrv 90[i8aqe3h79pgfw49U7[ZDER5-679

@stackallocator enp0s3 🥴

@stackallocator I remember having to edit config files with mac addresses in them in order to get boot order right in servers 20 years ago. Shit got crazy if you had to bond multiple ports too and they suddenly came up in a different order.

@stackallocator I plugged in a SAS card and it messed up my ethernet config. No guide helped and I had to reinstall my OS to make it work. Occured on Debian but not on Arch which is why Arch is better.