There's a lot of useful information there. It's unfortunate that the way in which it is expressed is likely to antagonise rather than teach.
Some of the older Linux people were terrific in the amount of work they put into educating people, but some software types have always been a bit high-handed, whether they specialised in Linux or something else.
some desktop linux distros solve it by using "udev" rules,
viz: (details changed to protect the guilty)
jasen@fozzie:~$ cat /etc/udev/rules.d/70-persistent-net.rules # # This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key.
# PCI device 0x8086:0x4236 (iwlagn) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:00:ff:11:22", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
# PCI device 0x8086:0x10f5 (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1c:33:ff:22:14", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
jasen@fozzie:~$
raspbpian doesn't do this, perhaps this is so that SD cards can be exchanged between hosts without having the changing MAC address mess all the networking up.
there's a no-coding method:
/dev/serial/by-path/
same socket, same hub => same name
the names are naot particularly mnemonic, but they are predictable.
Have something to add? Share your thoughts — no account required.
Ask the community — no account required