From owner-freebsd-current@FreeBSD.ORG Thu Dec 22 07:20:58 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 DDE28106566C; Thu, 22 Dec 2011 07:20:58 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 407E68FC08; Thu, 22 Dec 2011 07:20:58 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id pBM7KvAM087134; Thu, 22 Dec 2011 11:20:57 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id pBM7Kvj4087133; Thu, 22 Dec 2011 11:20:57 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 22 Dec 2011 11:20:57 +0400 From: Gleb Smirnoff To: Doug Barton Message-ID: <20111222072056.GJ80057@glebius.int.ru> 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> <4EF2430B.5070903@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4EF2430B.5070903@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current , Brooks Davis , 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: Thu, 22 Dec 2011 07:20:59 -0000 On Wed, Dec 21, 2011 at 12:35:23PM -0800, Doug Barton wrote: D> > On Tue, Dec 20, 2011 at 07:52:41PM -0600, Brooks Davis wrote: D> > B> While this is the documented path, it's not actually been required D> > B> except in edge cases for ages (the last I can remember is a.out->elf). D> > B> It's been long enough that I don't think we can really make people do D> > B> it except for a short period of time in HEAD. I believe it's D> > B> unacceptable for a release to release upgrade. D> > D> > I have provided API compatibility in r228768. I have tested it with an D> > ifconfig binary taken from 9.0 installation. D> D> So does that mean that if I upgrade to the latest HEAD from a system D> built before the ifconfig changes that when I reboot my network will D> come up? Yes, older infconfig will work in "head < r228571 || head > r228768". D> I think Brooks raised some really good points about backward D> compatibility, but it sounds to me like you've addressed them. In any D> case, my original concern was limited to "Do we need an UPDATING entry?" :) r228571 put an updating entry. D> > Since subject mentions "dhclient", I must notice that the dhclient-script D> > always relied on a bug in in_control(). The bug was fixed here: D> > D> > http://svnweb.freebsd.org/base?view=revision&revision=228313 D> > D> > Later the dhclient-script was fixed: D> > D> > http://svnweb.freebsd.org/base?view=revision&revision=228463 D> D> Right, I saw those go by, which is why I tried not to jump too hard on D> "ifconfig is broken" since I wasn't sure which change was causing my D> problem. It sounds like you're saying that perhaps I still won't be able D> to get the network up after booting a new kernel without also installing D> part of the new world? Perhaps an UPDATING entry is needed after all? On the second thought, I understand that r228313 breaks the dhclient-script only for people running two DHCP interfaces. If one obtains default route, then second can't run dhclient. I'm afraid, if we would try to document every kernel<->userland API/ABI change in head/ in the UPDATING, then the file will grow extremely quickly, and still many issues will be forgotten to be added there. -- Totus tuus, Glebius.