From owner-freebsd-emulation@FreeBSD.ORG Tue May 5 19:11:50 2009 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 4735B1065673; Tue, 5 May 2009 19:11:50 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id F1DB98FC1C; Tue, 5 May 2009 19:11:49 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from gate.ipt.ru ([194.62.233.123] helo=h30.sp.ipt.ru) by services.ipt.ru with esmtp (Exim 4.54 (FreeBSD)) id 1M1Q3Q-000E69-4g; Tue, 05 May 2009 23:11:48 +0400 To: Chagin Dmitry References: <81924694@bb.ipt.ru> <20090505144955.16373k1b32dpaxo0@webmail.leidinger.net> <47993241@bb.ipt.ru> <20090505160827.1359651x47bqmxc8@webmail.leidinger.net> <67678219@bb.ipt.ru> <20090505160724.GB14703@dchagin.static.corbina.ru> <35513746@bb.ipt.ru> <20090505184159.GA18677@dchagin.static.corbina.ru> From: Boris Samorodov Date: Tue, 05 May 2009 23:11:47 +0400 In-Reply-To: <20090505184159.GA18677@dchagin.static.corbina.ru> (Chagin Dmitry's message of "Tue\, 5 May 2009 22\:41\:59 +0400") Message-ID: <80154524@h30.sp.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Alexander Leidinger , freebsd-emulation@freebsd.org Subject: Re: [linux-f10] linux_socketcall... ERR#43 'Protocol not supported' 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, 05 May 2009 19:11:50 -0000 On Tue, 5 May 2009 22:41:59 +0400 Chagin Dmitry wrote: > On Tue, May 05, 2009 at 08:41:01PM +0400, Boris Samorodov wrote: > > On Tue, 5 May 2009 20:07:24 +0400 Chagin Dmitry wrote: > > > On Tue, May 05, 2009 at 07:26:28PM +0400, Boris Samorodov wrote: > > > > > > May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 > > > > May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > > > > May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 > > > > May 5 19:10:34 bb kernel: bsam: Entering linux_socketcall. > > > > May 5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0 > > > > May 5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2 > > > > May 5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43 > > > > ----- > > > > > > > > Corresponding text for linux_kdump and truss: > > > > ftp://ftp.ipt.ru/pub/linux/linux_kdump.ping.txt > > > > ftp://ftp.ipt.ru/pub/linux/truss.ping.txt > > > > > > > > > heh, it seems to me that SOCK_CLOEXEC, SOCK_NONBLOCK bits used. > > > should be fixed. socketpair() also uses it since 2.6.29 > > > > I'll be glad to test patches. > dchagin# ./ping ya.ru > WARNING: setsockopt(ICMP_FILTER): Protocol not available > WARNING: your kernel is veeery old. No problems. > PING ya.ru (213.180.204.8) 56(84) bytes of data. > ping: recvmsg: Invalid argument > ping: recvmsg: Invalid argument > So, more work nedeed. At least from 2.6.16 to 2.6.23 :) If ya.ru is not listed at your /etc/hosts, that may be enough (for now). I got such result with localhost and it's FQDN, and programs (linux-seamonkey, etc.) work with them. Can you send me your patch(es)? WBR -- bsam