From owner-freebsd-current@FreeBSD.ORG Wed Dec 21 16:37:23 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 612EE106566B; Wed, 21 Dec 2011 16:37:23 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) by mx1.freebsd.org (Postfix) with ESMTP id EE5118FC1B; Wed, 21 Dec 2011 16:37:21 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.4/8.14.4) with ESMTP id pBLGaFu6089664; Wed, 21 Dec 2011 10:36:15 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.4/8.14.4/Submit) id pBLGaAuG089663; Wed, 21 Dec 2011 10:36:10 -0600 (CST) (envelope-from brooks) Date: Wed, 21 Dec 2011 10:36:10 -0600 From: Brooks Davis To: Gleb Smirnoff Message-ID: <20111221163610.GA89546@lor.one-eyed-alien.net> References: <4EEF0124.4000902@FreeBSD.org> <4EEF3B22.8010401@FreeBSD.org> <4EF0499D.4070000@FreeBSD.org> <20111220191520.GA70684@FreeBSD.org> <20111221015241.GE68792@lor.one-eyed-alien.net> <20111221125539.GF70684@glebius.int.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: <20111221125539.GF70684@glebius.int.ru> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current , Doug Barton , Dimitry Andric Subject: Re: r228700 can't dhclient em0 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: Wed, 21 Dec 2011 16:37:23 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 21, 2011 at 04:55:40PM +0400, Gleb Smirnoff wrote: > Brooks, >=20 > On Tue, Dec 20, 2011 at 07:52:41PM -0600, Brooks Davis wrote: > B> While this is the documented path, it's not actually been required > B> except in edge cases for ages (the last I can remember is a.out->elf). > B> It's been long enough that I don't think we can really make people do > B> it except for a short period of time in HEAD. I believe it's > B> unacceptable for a release to release upgrade. >=20 > I have provided API compatibility in r228768. I have tested it with an > ifconfig binary taken from 9.0 installation. I hope, this change > would satisfy you, and you won't say that "We almost certainly need to > back r228571 out". Thank you! I spoke too strongly there. I was worried that we would=20 end up in an untenable situation, but you appear to have resolved it. > The in_control() and in6_control() are getting more and more hairy :( > I'd eager to remove the shim in the 11.x timeline. > Since subject mentions "dhclient", I must notice that the dhclient-script > always relied on a bug in in_control(). The bug was fixed here: >=20 > http://svnweb.freebsd.org/base?view=3Drevision&revision=3D228313 >=20 > Later the dhclient-script was fixed: >=20 > http://svnweb.freebsd.org/base?view=3Drevision&revision=3D228463 >=20 > So, if we are claiming for an undocumented but important feature > that new kernel being capable to configure network with world from > a previous major release, then I should merge r228463 right now > to stable/9, and not merge r228313. >=20 > If I don't merge r228463 before 9.0-RELEASE is out, then in > 2 years, 10.x-RELEASE kernel won't bring network up via DHCP with > world from 9.0-RELEASE. Thus, should I now either bribe re@ to push > r228463 prior to release, either back out the bugfix: r228463. You and bz have convinced me that for the configuration tools tools this change breaks, that it should be OK to have only supported 9.x releases (or possibly even only the last 9.x release) be able to upgrade without extra effort. I took too strong a position to start out. > Also, backing out r228463 would require backing out a larger > work: r228455. >=20 > Hey, this policy greatly discourages hacking on bugs and new > features... :( I hope we're approaching a more acceptable position... I don't want to discourage fixing bugs or adding features and more than having to deal with users inevitably does. -- Brooks --envbJBWh7q8WU6mo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFO8gr6XY6L6fI4GtQRAoI9AJ9DOTfVSMJaN7MM+5RTQ/tead7WzwCglqFc djBEiK3Ql5GwLrNOA+MGZl8= =pzqb -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--