On 31/03/13 14:53, Andrew Shadura wrote: > However, we had it without -1 for at least one release before; > actually, neither variant solves all the issues, so it seems the best > thing to do now is to stick to what we've had in squeeze.
Actually I agree now that removing the -1 flag is safest (reverting to squeeze behaviour). squeeze->wheezy upgraded systems would be at risk otherwise. If for any reason the DHCP server is unavailable at boot time, or requests are unanswered within the 60-second timeout (perhaps merely due to packet loss), we often *don't* want to abort bringing up that interface. Remote filesystems like NFS may be critical for the system to boot. Some daemons may not start up properly if a configured listen IP isn't assigned to any interfaces. And the administrator may be unable to control that system after their DHCP server or link comes back. Important bugs #694541 and #699947 both arose due to `dhclient -1` and are to some extent fixed by reverting it. On the other hand, impatient users may want to continue booting despite DHCP timeouts, especially on a laptop or desktop. They tend to have local access though where it's less of a disaster. IIRC, Ctrl-C may or may not allow them to skip past this, depending on the init system being used. But this would be the situation already on squeeze. Fresh wheezy installs are likely to use network-manager which I imagine behaves nicer for this use case. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51605c32.6070...@pyro.eu.org
