On Tue, 29 May 2012 14:47:58 +0200 Andrew Shadura <bugzi...@tut.by> wrote:
> I agree with many points of yours, but please explain how does it > break the boot sequence. Networking initscript allows ifup to fail as > far as I can see. How exactly does it break for you? "pppd persist maxfail 0 updetach" does not return until the PPP link comes up. If this does not happen for some reason, it never returns at all, and the boot sequence stops before any console is available, even in recovery mode. It's easy to reproduce the problem: enable the "persist" and "maxfail 0" options, unplug the ethernet cable to the modem, and reboot. Simple solution: take the "updetach" out of the ifup binary, as it was until recently, and if necessary, put it in /etc/network/interfaces, since this is now allowed to specify arbitrary options. Better solution: find some dependency mechanism with hotplug or udev that also works for DHCP or any other network configuration system. There's no valid reason why the entire boot sequence should have to wait until some WAN interface comes up; anything that actually depends on that happening should find some other way of noticing it. -- Ian Bruce -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
