Date: Tue, 24 Jul 2007 22:41:05 +0200 From: Roman Divacky <rdivacky@freebsd.org> To: John Nielsen <lists@jnielsen.net> Cc: freebsd-emulation@freebsd.org Subject: [PATCH]: linux ioctls not implemented - advice? Message-ID: <20070724204105.GA30450@freebsd.org> In-Reply-To: <20070724201924.GA29874@freebsd.org> References: <200707241545.59049.lists@jnielsen.net> <20070724201924.GA29874@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 24, 2007 at 10:19:24PM +0200, Roman Divacky wrote: > > 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? www.vlakno.cz/~rdivacky/linux_socket.patch please report back... also.. it would be nice if this patch does not work that you can provide me strace from real linux. the second ioctl is not implemented on linux and I am not sure how to fake that.. thnx
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070724204105.GA30450>