Well, your links led me on a chase of the 3 solutions:
You disable the assignment of fixed names, so that the unpredictable kernel names are used again. For this, simply mask udev’s rule file for the default policy: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
Did not work as that rules statement does not exist
You create your own manual naming scheme, for example by naming your interfaces “internet0”, “dmz0” or “lan0”. For that create your own .link files in /etc/systemd/network/, that choose an explicit name or a
better naming scheme for one, some, or all of your interfaces.
See systemd.link(5) for more information.
Did not work, network stopped working
You pass the net.ifnames=0 on the kernel command line
Did not work, network stopped working
What happens is that although I got the bootup to stop renaming the interfaces, it just stopped and did not name them anything.
I renamed /lib/systemd/network/90-mac-for-usb.link and /lib/systemd/network/91-default.link to *.backup and then made my own link file: /lib/systemd/network/95-pirate.link with the following:
[Match]
MACAddress=b8:27:eb:52:45:cc
[Link]
Name=eth0
[Match]
MACAddress=00:21:2f:39:8e:53
[Link]
Name=wlan0
ref: http://wiki.beyondlogic.org/index.php?title=Understanding_RaspberryPi_Boot_Process , http://www.freedesktop.org/software/systemd/man/systemd.link.html
To no avail, with either the backup files in place or not. Tried different number schemes in case the files are read in numbered order. I’m pretty ticked off at this point as it’s really cumbersome on my system to switch monitor modes and my tiny wireless keyboard. When the network is working I can at least SSH into the PI.
All this just to get a program, PirateBox to work as it calls to interface wlan0 to get going.