Bug#838871: ifupdown: attempts to bring up allow-hotplug interfaces at boot ignoring link state

2020-10-20 Thread Santiago Ruano Rincón
Control: tags -1 + pending On Sun, 25 Sep 2016 17:31:23 -0400 manul wrote: > Package: ifupdown > Version: 0.8.16 > Severity: normal > > Dear Maintainer, > > My laptops cable interface eth0 is listed in /etc/network/interfaces, using > the following stanza: > > >> allow-hotplug eth0 > >> ifac

Bug#838871: ifupdown: attempts to bring up allow-hotplug interfaces at boot ignoring link state

2019-05-23 Thread 838871
Dear Maintainer, The bug still persists on fresh stretch and buster installations. Is there any chance this could get fixed, or could you close this bug with a wontfix and give a reason on why it's not? Seeing that the bug persists for 3 years now. Thank you. Information for other people r

Bug#838871: ifupdown: attempts to bring up allow-hotplug interfaces at boot ignoring link state

2017-04-16 Thread Stanisław
I confirm the bug. I have a laptop and usually I use WLAN instead of cable connection. In such a case booting process stops for a few minutes with a statment "ifup: waiting for lock on /run/network/interfaces/ifstate.eth0". Dear Maintainer, could you, please, revert to previous behavior?

Bug#838871: ifupdown: attempts to bring up allow-hotplug interfaces at boot ignoring link state

2016-09-29 Thread Guus Sliepen
On Thu, Sep 29, 2016 at 10:28:20AM +0200, Frank Gevaerts wrote: > 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 > tha

Bug#838871: ifupdown: attempts to bring up allow-hotplug interfaces at boot ignoring link state

2016-09-29 Thread Frank Gevaerts
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

Bug#838871: ifupdown: attempts to bring up allow-hotplug interfaces at boot ignoring link state

2016-09-26 Thread Guus Sliepen
On Sun, Sep 25, 2016 at 05:31:23PM -0400, manul wrote: > As per man interfaces 5, I want my eth0 interface to be brought up (and > dchp-initialized) only when the link gets up (cable gets connected). Actually, the manpage does not mention that hotplug interfaces are brought up only when a link i

Bug#838871: ifupdown: attempts to bring up allow-hotplug interfaces at boot ignoring link state

2016-09-25 Thread manul
Package: ifupdown Version: 0.8.16 Severity: normal Dear Maintainer, My laptops cable interface eth0 is listed in /etc/network/interfaces, using the following stanza: >> allow-hotplug eth0 >> iface eth0 inet dhcp The reason I use allow-hotplug is: As per man interfaces 5, I want my eth0 inte