From owner-svn-src-all@FreeBSD.ORG Thu Apr 9 15:51:58 2009 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41006106566B; Thu, 9 Apr 2009 15:51:58 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id EBA6F8FC19; Thu, 9 Apr 2009 15:51:57 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LrwXm-00017i-CM; Thu, 09 Apr 2009 19:51:58 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id B13B37C9A; Thu, 9 Apr 2009 19:52:08 +0400 (MSD) Received: by hades.panopticon (Postfix, from userid 1000) id 56EAE10883A; Thu, 9 Apr 2009 19:51:38 +0400 (MSD) Date: Thu, 9 Apr 2009 19:51:38 +0400 From: Dmitry Marakasov To: Brooks Davis Message-ID: <20090409155138.GD7795@hades.panopticon> References: <200903191248.n2JCm0Rd061331@svn.freebsd.org> <20090409131253.GB7795@hades.panopticon> <20090409153805.GB83847@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20090409153805.GB83847@lor.one-eyed-alien.net> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Dag-Erling Smorgrav Subject: Re: svn commit: r190031 - head/etc/defaults X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2009 15:51:58 -0000 * Brooks Davis (brooks@FreeBSD.org) wrote: > > Shouldn't synchronous_dhclient be ON by default then? The way it > > is, DHCP is not used at all, I ended up with unreachable box which > > didn't get any IP already. > > Unless you have one of the few interfaces that does not generate > link status events, dhclient will be started by devd. The only ones I > know of are a subset set of ed(4) devices, though I think imp may have > fixed those recently with a stub ifmedia interface. I use ale(4). Will test some more. Couldn't the fact that the interface is renamed be the reason? Also, how is the issue of services not starting because of no default route/dns/network available solved when running dhclient from devd? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru