From owner-freebsd-hackers Thu May 28 14:24:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28858 for freebsd-hackers-outgoing; Thu, 28 May 1998 14:24:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28848 for ; Thu, 28 May 1998 14:24:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA01468; Thu, 28 May 1998 13:17:24 -0700 (PDT) Message-Id: <199805282017.NAA01468@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andrzej Bialecki cc: "Daniel O'Connor" , Julian Elischer , Nicholas Charles Brawn , Ollivier Robert , hackers@FreeBSD.ORG Subject: Re: Linux emulation failure (was Star-office) In-reply-to: Your message of "Thu, 28 May 1998 22:56:22 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 13:17:23 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 28 May 1998, Daniel O'Connor wrote: > > > > try truss, as that gives better information under linux emulation I'm > > > told. > > OK, I'll give it a go > > I kinda remember from some linux talk that they started to use glibc in > the newest SO4.0 release instead of normal linux libc... This could be the > cause. Thanks for the confirmation; the bogon is about right for glibc's generally pretty poor standard. I wonder what the SCO people are doing, now that they have given up on a source-level compatibility and are chasing Linux binary compatibility. I guess I should do something with the ODT pile here. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message