From owner-freebsd-hackers Thu Sep 24 15:30:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00435 for freebsd-hackers-outgoing; Thu, 24 Sep 1998 15:30:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00352 for ; Thu, 24 Sep 1998 15:30:05 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id PAA14554; Thu, 24 Sep 1998 15:29:56 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd014519; Thu Sep 24 15:29:47 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id PAA10429; Thu, 24 Sep 1998 15:29:46 -0700 (MST) From: Terry Lambert Message-Id: <199809242229.PAA10429@usr02.primenet.com> Subject: Re: How can I run glibc Linux binaries (RedHat 5.x) on FreeBSD (CURRENT)? To: jake.hamby@jpl.nasa.gov (Jake Hamby) Date: Thu, 24 Sep 1998 22:29:46 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <360AAC61.4FE0E3A0@jpl.nasa.gov> from "Jake Hamby" at Sep 24, 98 01:32:33 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ ... ] > I'd like to help fix this problem myself, but I don't know where to > begin. I'm assuming that kdump prints the FreeBSD, instead of the Linux > syscalls, so I looked them up and old.recvfrom => mprotect(), while dup2 > => mmap() and #91 => munmap(). Looking at a ktrace from > /compat/linux/bin/sh, it appears that this is a fairly normal part of > startup, and looks like the shared libraries mapping in. > > The only really unusual thing my untrained eye can see is that both > /compat/linux/lib/ld-linux.so.1 and /compat/linux/lib/ld-linux.so.2 are > being loaded in. But I don't have any idea what to do about it. If I > try copying the newer ld-linux.so.2 as ld-linux.so.1, then FreeBSD > simply complains that it can't find ld-linux.so.1. > > Any ideas? Try again with truss. It uses the right system call names; SEF showed me that, specifically, as a feature of his implementation methodology. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message