it's not eth0 anymore, it's enp5s0
0 Boosts
0 Likes
This federated comment is not yet available here.
@hipsterelectron @arrjay @jiub actually kinda like that
@c0dec0dec0de @hipsterelectron @jiub *sigh* I deeply do not care for what systemd did, though. and wound up with a pile of systemd.link files to match on path/firmware/property=DEVPATH keys so all my crap reliably has wl and be([0|1]) interfaces. I still think that was a very arbitrary and painful break.
@arrjay @c0dec0dec0de @jiub after engaging poettering on the dlopen backdoor i am ruthless about any and all systemd hate. my body is a machine that turns keyboards into flaming systemd
@hipsterelectron @c0dec0dec0de @jiub no no, see, we just assume the user has NO AGENCY AT ALL and systemd's choices and defaults make sense
@arrjay @hipsterelectron @c0dec0dec0de @jiub I've been in more than one workplace where install scripts override systemd's device enumeration. The thing was, they'd do it in stupid, broken ways, that actually left me biased in favor of systemd, until a year or two ago.
(illumos/*BSD use the driver name as base)