On Wed 08 Jun 2011 at 16:06:34 +0000, Camaleón wrote: > It seems it can fail, at least under some scenarios ;-) > > ifupdown: /etc/init.d/networking should support allow-hotplug > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550014
This isn't a failure of allow-hotplug but a perceived defect in the /etc/init.d/networking script, which only takes account of auto. > If you add to this udev events and system restoration from a suspended > state, the mess can be royal. Not a problem the OP experienced. :) > There must be another similiar bugs out there because this is not the > first time I've read problems with the "*-hotplug" stanza. You have the advantage on me but I'm unpersuaded. The initial post was a classic dhcp couldn't get an address description. Now if he had said he was using static addressing (which just may be on the desktop machines he mentioned) I'd be stumped. Maybe Mitchell Laks could boot with allow-hotplug and with auto 20/30 times and report his observations. And another 20/30 times without either. Recording relevant boot messages of course and seeing what dmesg has to say about the state of eth0. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110608172744.GI19914@desktop
