From owner-freebsd-current@FreeBSD.ORG Wed Dec 13 13:03:33 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5FD5F16A416; Wed, 13 Dec 2006 13:03:33 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id A04B743C9F; Wed, 13 Dec 2006 13:01:46 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout2.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id kBDD1ru0031291; Wed, 13 Dec 2006 05:01:54 -0800 (PST) Date: Wed, 13 Dec 2006 22:01:52 +0900 Message-ID: From: gnn@freebsd.org To: Doug Barton In-Reply-To: <457D2655.9050500@FreeBSD.org> References: <457C81E9.7040806@FreeBSD.org> <457D2655.9050500@FreeBSD.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.90 (i386-apple-darwin8.8.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: re@freebsd.org, freebsd-current@freebsd.org Subject: Re: Socket problems with latest -current 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, 13 Dec 2006 13:03:33 -0000 At Mon, 11 Dec 2006 01:35:17 -0800, Doug Barton wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Doug Barton wrote: > > With sources cvsup'ed around 20:35 PST on 8 December everything works > > just fine. With sources cvsup'ed early this morning, 12:42 am PST on > > 10 December, I'm getting a lot of errors related to sockets: > > I found the problem, it's the change made in version 1.4 of > rc.d/auto_linklocal. Reverting only that change, and using otherwise > up to date -current sources allows things to work just fine. Adding > that change on the same exact system causes the breakage I described > in my previous message. > > It's probably worth mentioning that I exactly fit the criteria from > the 1.4 commit message, I have INET6 in my kernel, but at the moment I > have ipv6_enable=no in rc.conf. > > This change should be backed out of HEAD and RELENG_6[_2] until the > cause of this breakage is understood. I'll take a quick look at this too. Best, George