From owner-freebsd-stable Sat Jun 30 1:36: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dmz.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id 3D11037B405 for ; Sat, 30 Jun 2001 01:36:04 -0700 (PDT) (envelope-from roman@harmonic.co.il) Received: (from http@localhost) by dmz.harmonic.co.il (8.11.1/8.11.1) id f5U8at010635; Sat, 30 Jun 2001 11:36:55 +0300 (IDT) (envelope-from roman@harmonic.co.il) To: Valentin Nechayev Subject: Re: Unable to run linux unace Message-ID: <993890215.3b3d8fa7728a1@webmail.harmonic.co.il> Date: Sat, 30 Jun 2001 11:36:55 +0300 (IDT) From: Roman Shterenzon Cc: freebsd-stable@freebsd.org References: <993766542.3b3bac8e564d4@webmail.harmonic.co.il> <993772061.3b3bc21db3df0@webmail.harmonic.co.il> <20010629205043.A738@iv.nn.kiev.ua> In-Reply-To: <20010629205043.A738@iv.nn.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Quoting Valentin Nechayev : > Fri, Jun 29, 2001 at 02:47:41, roman (Roman Shterenzon) wrote about > "Re: Unable to run linux unace": > > > > -- UNKNOWN SYSCALL 221 > > > (null)() ERR#78 'Function > not > > > implemente > > > d' > > Let's believe in correctness of these syscall numbers (see below > why)... > 221 is sys_fcntl64 in 2.4.1 and does not exist in 2.2.16. > > > > -- UNKNOWN SYSCALL 201 > > 201 is sys_geteuid in 2.4.1 and does not exist in 2.2.16. > 2.2.16 has sys_geteuid as syscall 49. 2.4.1 declares it as > sys_geteuid16. > > > This is what I get when I run it on remote linux system: > > Version of kernel of this linux system may be essential to diagnose. > > But I'm surprised that linux trace mentions shmat() and semop() > (which are implemented in linux in generic sys_ipc() multiplexer, > syscall number 117), but your FreeBSD trace says quite another > numbers. > Possibly these syscall numbers are not target to believe. > > > execve("./unace", ["./unace"], [/* 27 vars */]) = 0 > > shmat(0, 0, 0x1) = -1 ENOSYS (Function not > implemented) > > fcntl(0, F_GETFD) = 0 > > fcntl(1, F_GETFD) = 0 > > fcntl(2, F_GETFD) = 0 > > uname({sys="Linux", node="xxxx.yyyy.com", ...}) = 0 > > semop(131601, 0, 38) = -1 ENOSYS (Function not > implemented) > > > /netch > The linux system I tried running unace on is 2.2.17. The FreeBSD sysctl emulates linux version of 2.2.12. Do you think that these syscalls are essential? Because they fail on both FreeBSD and Linux, perhaps they're not the main reason for the failure? Any ideas? Where is the linuxulator guy? :) --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message