From owner-freebsd-current@FreeBSD.ORG Tue Nov 17 00:29:08 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 3457C106568F for ; Tue, 17 Nov 2009 00:29:08 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id AFD128FC12 for ; Tue, 17 Nov 2009 00:29:07 +0000 (UTC) Received: (qmail 9903 invoked by uid 399); 17 Nov 2009 00:29:06 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 17 Nov 2009 00:29:06 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B01EE51.2040904@FreeBSD.org> Date: Mon, 16 Nov 2009 16:29:05 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Rui Paulo References: <4B0087C2.9070508@FreeBSD.org> <4B00BA99.5000009@FreeBSD.org> <3a142e750911160035m520819eqdf261c0c493bf3c3@mail.gmail.com> <4B01B66F.1040903@FreeBSD.org> <4B01C3A6.5060101@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: wpa_supplicant + wpi0 won't lock in on today's -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: Tue, 17 Nov 2009 00:29:08 -0000 Rui Paulo wrote: > On 16 Nov 2009, at 21:27, Doug Barton wrote: > >> Doug Barton wrote: >>> Rui, it would be nice to include a note about this in UPDATING. >> To be fair someone else drew my attention to the fact that there is an >> entry in UPDATING about the change, however it doesn't mention >> wpa_supplicant, and merely recompiling wpa_supplicant wasn't >> sufficient to fix the problem, so perhaps that entry could be expanded. > > Well, when I did this change I did build with -DNOCLEAN and it rebuilt a good wpa_supplicant. I'm not in any way implying that you did not test the change thoroughly. Please let me know your intentions regarding the UPDATING entry. I'll be glad to augment it myself if necessary. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/