-pi-nostart network-manager
-# make networkmanager use resolvconf instead of its own dnsmasq which
-# conflicts with the normal dnsmasq package.
-f=/etc/NetworkManager/NetworkManager.conf
-m=$(md5sum $f)
-sudo sed -ri '/ *\[main\]/,/^ *\[[^]]+\]/{/^\s*dns[[:space:]=]/d}' $f
-sudo sed -ri '/ *\[main\]/a dns=default' $f
-if [[ $m != $(md5sum $f) ]]; then
- srestart NetworkManager
-fi
+case $(debian-codename) in
+ # needed for debootstrap scripts for fai since fai requires debian
+ flidas)
+ pi dnsmasq
+ pi-nostart network-manager
+ # make networkmanager use resolvconf instead of its own dnsmasq which
+ # conflicts with the normal dnsmasq package.
+ f=/etc/NetworkManager/NetworkManager.conf
+ m=$(md5sum $f)
+ sudo sed -ri '/ *\[main\]/,/^ *\[[^]]+\]/{/^\s*dns[[:space:]=]/d}' $f
+ sudo sed -ri '/ *\[main\]/a dns=default' $f
+ if [[ $m != $(md5sum $f) ]]; then
+ srestart NetworkManager
+ fi
+ # networkmanager has this nasty behavior on flidas: if the machine
+ # crashes with dnsmasq running, on subsequent boot, it adds an entry to
+ # resolvconf for 127.0.0.1 in some stupid attempt to restore
+ # nameservers.
+ # This can be manually fixed by stoping dnsmasq,
+ # then based on whats in /run/dnsmasq/, i see we can run
+ # s resolvconf -d NetworkManager
+ # oh ya, and stoping NetworkManager leaves this crap behind without cleaning it up.
+ ser disable NetworkManager
+ ;;
+esac