From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 18:12:10 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id 04F631065670; Tue, 21 Aug 2012 18:12:10 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id C1CFE14D950; Tue, 21 Aug 2012 18:12:09 +0000 (UTC) Message-ID: <5033CF7A.8080406@FreeBSD.org> Date: Tue, 21 Aug 2012 11:12:10 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: John Baldwin References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> In-Reply-To: <201208210934.31484.jhb@freebsd.org> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , freebsd-current@freebsd.org, lev@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 18:12:10 -0000 On 8/21/2012 6:34 AM, John Baldwin wrote: > Humm. devd is the more common case, and we explicitly don't use devd to start > dhclient on boot even when devd is enabled (so out of the box dhcp would first > be started by rc, but would be restarted by devd). That sounds reasonable. People who choose not to run devd can be responsible for restarting dhclient themselves. > Another option is to rework dhclient to work like it does on OpenBSD where it > renews its lease if the link bounces, but to not exit when the link goes down. That would be preferable. > That case would fix the currently broken case that you unplug your cable, take > your laptop over to another network (e.g. take it home if suspend/resume > works), then plug it back in and are still stuck with your old IP. I do think it's important to fix this case. However I agree with the chorus of responders that it is more important to maintain our historic resilience to temporary loss of connectivity. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909)