From owner-freebsd-emulation@FreeBSD.ORG Tue Jul 24 20:19:30 2007 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5168116A417 for ; Tue, 24 Jul 2007 20:19:30 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (vlk.vlakno.cz [62.168.28.247]) by mx1.freebsd.org (Postfix) with ESMTP id 0E04613C45B for ; Tue, 24 Jul 2007 20:19:27 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 2E1D38C034A; Tue, 24 Jul 2007 22:19:26 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (vlk.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fC4kT1fmyBD5; Tue, 24 Jul 2007 22:19:25 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 121338BF8F7; Tue, 24 Jul 2007 22:19:25 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.13.8/8.13.8/Submit) id l6OKJOvf029986; Tue, 24 Jul 2007 22:19:24 +0200 (CEST) (envelope-from rdivacky) Date: Tue, 24 Jul 2007 22:19:24 +0200 From: Roman Divacky To: John Nielsen Message-ID: <20070724201924.GA29874@freebsd.org> References: <200707241545.59049.lists@jnielsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200707241545.59049.lists@jnielsen.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-emulation@freebsd.org Subject: Re: linux ioctls not implemented - advice? X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2007 20:19:30 -0000 > Two attempts to use ioctl 0x8938 and four attempts to use ioctl 0x8933 every > time I start the executable (regardless of login attempts). > > The message is fairly explanatory; my question is what can I do about it? Is > there a canonical list of Linux ioctls anywhere that would tell me what this > binary is trying to do? From the behavior I'm seeing and from looking at > linux_ioctl.h I suspect that they belong in the "socket" category, but that's > as far as I've gotten. #define SIOCGIFINDEX 0x8933 /* name -> if_index mapping */ #define SIOCGIFCOUNT 0x8938 /* get number of devices */ I might look at at. should not be that hard to implement those. are you willing to test patches? roman