From owner-freebsd-current@FreeBSD.ORG Mon Sep 28 13:24:04 2009 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 945BD106566C for ; Mon, 28 Sep 2009 13:24:04 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay3.uni-muenster.de (ZIVM-EXRELAY3.UNI-MUENSTER.DE [128.176.192.20]) by mx1.freebsd.org (Postfix) with ESMTP id 264798FC1D for ; Mon, 28 Sep 2009 13:24:03 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,466,1249250400"; d="scan'208";a="14430802" Received: from zivmaildisp2.uni-muenster.de (HELO ZIVMAILUSER05.UNI-MUENSTER.DE) ([128.176.188.143]) by zivm-relay3.uni-muenster.de with ESMTP; 28 Sep 2009 15:24:02 +0200 Received: by ZIVMAILUSER05.UNI-MUENSTER.DE (Postfix, from userid 149459) id 5BDBF1B07E5; Mon, 28 Sep 2009 15:24:02 +0200 (CEST) Date: Mon, 28 Sep 2009 15:24:02 +0200 (CEST) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , Andriy Gapon Message-ID: In-Reply-To: <86my4f45c6.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@FreeBSD.org Subject: Re: ipv6 related warnings 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: Mon, 28 Sep 2009 13:24:04 -0000 Dag-Erling Sm=F8rgrav schrieb am 2009-09-28: > Andriy Gapon writes: > > Dag-Erling Sm=F8rgrav writes: > > > No, you can build a *kernel* without IPv6, just not userland. > > > Parts > > > of userland will respect WITHOUT_INET6, others won't, and others > > > yet > > > will build but not run correctly. > > So shouldn't those disrespecting parts of userland be fixed? > Why? In most (userland) cases, it takes more work to write code that > supports IPv4 but not IPv6 than to write code that supports both. > > Besides, returning to the original post, those messages weren't > > there > > just a few days ago, this is a new addition. > ...if by "just a few days" you mean "two weeks". If this really is > "a > new addition", it dates back to one of hrs@'s commits on 2009-09-13. > However, the most likely cause of the OP's problem is incorrect use > of > mergemaster. If he did indeed run "mergemaster -p" and "mergemaster > -i", but nothing more, his /etc is completely out of sync. mergemaster -p and mergemaster -i aren't sufficient to sync /etc with /usr/src/etc? but that's what UPDATING recommends. alex > DES