Note to myself: We already have this logic for upgrading virtualized hosts:
# we enabled net.ifnames in 220-7 by default; don't change iface names in
# virtualized envs (where 75-persistent-net-generator.rules didn't work)
if dpkg --compare-versions "$2" lt-nl "220-7~" &&
[ ! -e /etc/udev/rules.d/70-persistent-net.rules ] &&
[ ! -e /etc/udev/rules.d/80-net-setup-link.rules ] &&
! grep -q net.ifnames /proc/cmdline ; then
mkdir -p /etc/udev/rules.d
cat <<EOF > /etc/udev/rules.d/80-net-setup-link.rules
# This machine is most likely a virtualized guest, where the old persistent
# network interface mechanism (75-persistent-net-generator.rules) did not work.
# This file disables /lib/udev/rules.d/80-net-setup-link.rules to avoid
# changing network interface names on upgrade. Please read
# /usr/share/doc/udev/README.Debian.gz about how to migrate to the currently
# supported mechanism.
EOF
fi
We enabled ifnames in 220-7. But apparently VMWare devices naming changed after wily's 225.
Note to myself: We already have this logic for upgrading virtualized hosts:
# we enabled net.ifnames in 220-7 by default; don't change iface names in net-generator. rules didn't work) rules.d/ 70-persistent- net.rules ] && rules.d/ 80-net- setup-link. rules ] && rules.d/ 80-net- setup-link. rules net-generator. rules) did not work. rules.d/ 80-net- setup-link. rules to avoid doc/udev/ README. Debian. gz about how to migrate to the currently
# virtualized envs (where 75-persistent-
if dpkg --compare-versions "$2" lt-nl "220-7~" &&
[ ! -e /etc/udev/
[ ! -e /etc/udev/
! grep -q net.ifnames /proc/cmdline ; then
mkdir -p /etc/udev/rules.d
cat <<EOF > /etc/udev/
# This machine is most likely a virtualized guest, where the old persistent
# network interface mechanism (75-persistent-
# This file disables /lib/udev/
# changing network interface names on upgrade. Please read
# /usr/share/
# supported mechanism.
EOF
fi
We enabled ifnames in 220-7. But apparently VMWare devices naming changed after wily's 225.