I read quite a lot of the answers to your post, and I still think there is a
problem, not
linked to the kernel's interface name name. I have a wifi interface named
*everywhere*
wlan0. It isn't found by network-pre.target, network-target or
networking-service, I
don't know which one. What I know is bind9 (named in fact) can't start, because
/etc/insserv.conf asks for $network to start $named; after boot, when network
is
started there is no problem starting named by hand with:
"named -u named -t /my-chroot-dir -c /etc/named.conf"
but bind9.service doesn' start and tells me:
Drop-In: /run/systemd/generator/bind9.service
└─50-insserv.conf-$named.conf
I suppose it's a bug, but as it works like this!! (See bind9-named post in
debian-user-
french list
Jacques
