From owner-freebsd-hackers Thu Dec 7 09:48:57 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA02621 for hackers-outgoing; Thu, 7 Dec 1995 09:48:57 -0800 (PST) Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA02598 for ; Thu, 7 Dec 1995 09:48:45 -0800 (PST) Received: (from news@localhost) by haywire.DIALix.COM (sendmail) id BAA07933 for freebsd-hackers@freebsd.org; Fri, 8 Dec 1995 01:48:37 +0800 (WST) Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-hackers@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-hackers@freebsd.org Date: 8 Dec 1995 01:48:32 +0800 From: peter@haywire.dialix.com (Peter Wemm) Message-ID: <4a79dg$7np$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <18636.818246983@time.cdrom.com>, <199512061446.IAA25559@jake.lodgenet.com> Subject: Re: Getting linux netscape binary to work? Sender: owner-hackers@freebsd.org Precedence: bulk erich@lodgenet.com (Eric L. Hernes) writes: >Now the biggest problem I see is that my syslog fills up with: >Linux-emul(17199): syslog() not supported (BSD sigreturn) This has _got_ to be a bug.. :-( there are two syslog() functions in Linux BTW. syslog(2) is a method of controlling and reading the kernel console messages. syslog(3) is what we normally expect from syslog(). Why Netscape is calling syslog(2) over and over again and hence getting this message is beyond me. As long as it's not running as root, it *cannot* *do* anything with this system call. I suspect it's a linker botch or a libc.so.4.5.26 (the version in ports linux-lib package) where the wrong thing is being called. :-( I'd be enclined to suggest that the linux_syslog() syscall stub should return EPERM if not being run as root (same as linux) and only print the message if it is being run as root (bad idea! btw) -Peter >eric. >-- >erich@lodgenet.com >erich@rrnet.com