toast@donotsta.re
@toast@donotsta.re
Posts
-
i love alcohol -
i love alcohol@Lilith what is lilith's favorite alcohol -
That's a new one.@domi @azonenberg@ioc.exchange hello from enx5847[censored]
I was going to go into the deep end but turns out the same script used for "predictable inames" actually exports this information too, but never uses it in the default script
looks like so to get this working:ACTION!="add", GOTO="net_name_slot_end" SUBSYSTEM!="net", GOTO="net_name_slot_end" NAME!="", GOTO="net_name_slot_end" IMPORT{cmdline}="net.ifnames" ENV{net.ifnames}=="0", GOTO="net_name_slot_end" NAME=="", ENV{ID_NET_NAME_MAC}!="", NAME="$env{ID_NET_NAME_MAC}" LABEL="net_name_slot_end"save as /etc/udev/rules.d/80-net-name-slot.rules
the line starting withNAME==""is the only important one realistically
it does look like$attr{address}should also match but then you have to add the en/wl/etc prefix yourself (which could probably be done using KERNEL==… I might poke at that after my meeting) -
That's a new one.@domi @azonenberg hmm, you might be able to? cursory reading of udev(7) suggests ATTR{} is a thin layer over sysfs, and in sysfs you have device/address which contains the MAC… -
That's a new one.@domi @azonenberg I should write this udev rule :^) (actually can you? I'm not sure udev is mac-aware)