From owner-freebsd-current@FreeBSD.ORG  Wed Nov 19 15:01:05 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EFBD616A4E9
	for <freebsd-current@freebsd.org>;
	Wed, 19 Nov 2003 15:01:04 -0800 (PST)
Received: from smtp.fud.org.nz (203-79-110-29.cable.paradise.net.nz
	[203.79.110.29])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 740B6440E1
	for <freebsd-current@freebsd.org>;
	Wed, 19 Nov 2003 14:59:30 -0800 (PST)	(envelope-from andy@fud.org.nz)
Received: by smtp.fud.org.nz (Postfix, from userid 1001)
	id AD526170A5; Thu, 20 Nov 2003 11:59:27 +1300 (NZDT)
Date: Thu, 20 Nov 2003 11:59:27 +1300
From: Andrew Thompson <andy@fud.org.nz>
To: Ryan Sommers <ryans@gamersimpact.com>
Message-ID: <20031119225927.GB15434@kate.fud.org.nz>
References: <20031119223948.61677.qmail@neuroflux.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031119223948.61677.qmail@neuroflux.com>
User-Agent: Mutt/1.5.4i
cc: freebsd-current@freebsd.org
Subject: Re: DStumbler / BSD-AirTools Error with new Wi code?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2003 23:01:05 -0000

On Wed, Nov 19, 2003 at 05:39:48PM -0500, Ryan Sommers wrote:
> I have been getting the following error when attempting to use dstumbler 
> with 5.1-RELEASE-p10: 
> 
> error: unable to ioctl device socket: Invalid argument 
> 

You may want to cvsup, the port was updated 17 hours ago.

http://www.freebsd.org/cgi/getmsg.cgi?fetch=619842+0+current/cvs-ports


Andy