Package: ifupdown Version: 0.8.16 Followup-For: Bug #838871 First of all, I'm seeing exactly the same symptoms.
One problem with not looking at link state is that the interface is always powered up. As I understand it, on some laptops this can make a measurable difference. My own measurements are a bit inconclusive (powertop reports that eth0 uses 0.3W more with ifupdown 0.8.16 than with 0.8.13, but total battery drain seems to be the same), but I believe it's a good argument for providing a link state option anyway. Apart from that, clarifying (in the documentation) what "hotplug" actually means would be good. I think your definition of "the device appears" is entirely reasonable, but these things are confusing and it's unfortunate that the concepts of "the device is there" and "the cable is there" have been mixed up historically. Frank -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages ifupdown depends on: ii adduser 3.115 ii init-system-helpers 1.45 ii iproute2 4.6.0-4 ii libc6 2.24-3 ii lsb-base 9.20160629 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.5~b1-1 Versions of packages ifupdown suggests: ii ppp 2.4.7-1+3 pn rdnssd <none> -- no debconf information
