From owner-freebsd-current@FreeBSD.ORG Tue Dec 20 19:15:22 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 583EF1065678; Tue, 20 Dec 2011 19:15:22 +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 C92BE8FC17; Tue, 20 Dec 2011 19:15:21 +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 pBKJFKXH071293; Tue, 20 Dec 2011 23:15:20 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id pBKJFKeA071292; Tue, 20 Dec 2011 23:15:20 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 20 Dec 2011 23:15:20 +0400 From: Gleb Smirnoff To: Doug Barton Message-ID: <20111220191520.GA70684@FreeBSD.org> References: <4EEF0124.4000902@FreeBSD.org> <4EEF3B22.8010401@FreeBSD.org> <4EF0499D.4070000@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4EF0499D.4070000@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current , 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: Tue, 20 Dec 2011 19:15:22 -0000 Doug, On Tue, Dec 20, 2011 at 12:38:53AM -0800, Doug Barton wrote: D> > I saw this too, when my kernel and userland were out of sync (e.g. just D> > after installing a new kernel, and before installworld). I suspect it D> > is caused by the changes in r228571, which cause old ifconfig and D> > dhclient to not recognize any interfaces. I'm not 100% sure though... D> D> I tried replacing both ifconfig and dhclient with the versions that were D> built along with the new kernel, and that didn't work. This shouldn't happen. If you did 'make buildworld buildkernel', then your world in objdir would have binaries compiled with includes from source tree, not from /usr/include, thus compatible with new kernel. 'make buildworld buildkernel' always produces compatible kernel and worlds. However, if you did 'cd /usr/src/sbin/ifconfig && make all install' then that didn't work, since used headers from /usr/include. D> The traditional (and documented) upgrade process for many years has been D> to boot the new kernel, make sure it's Ok, then update world. Obviously D> something different is needed this time, so it needs an UPDATING entry D> (assuming that all this is not just a bug). The documented one says 'Reboot into single user mode' and then install new world. This path was not broken, since single user mode doesn't imply network support. The undocumented brave way 'make installkernel installworld && reboot' works also, without any problems. -- Totus tuus, Glebius.