From owner-freebsd-hackers Wed Mar 18 06:19:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16077 for freebsd-hackers-outgoing; Wed, 18 Mar 1998 06:19:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15968 for ; Wed, 18 Mar 1998 06:19:13 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id GAA07400; Wed, 18 Mar 1998 06:18:46 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: "Nate Williams" cc: Mark Newton , freebsd-hackers@FreeBSD.ORG Subject: Re: BSDI executables In-reply-to: Your message of "Wed, 18 Mar 1998 03:11:44 MST." <199803181011.DAA00841@nomad.mt.sri.com> Date: Wed, 18 Mar 1998 06:18:45 -0800 Message-ID: <7396.890230725@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, if you put all the FreeBSD shlibs onto a recent BSDi box, it > will run non-kernel binaries fine. Some things don't work (JDK didn't > work, but tcsh, kaffe, and ssh worked fine). Really? I managed to do this with an earlier (BSD/OS 1.x?) machine and it worked great - everything from FreeBSD emacs to fvwm binaries ran under BSD/OS with the FreeBSD ld.so and shared libs copied into the appropriate places. My copy of BSD/OS 2.1, however, simply refuses to execute the FreeBSD executable at all, shared or static. The image activator spits up on it, claiming it's of an invalid binary format. How did you manage to get it to work, that's what I want to know. ;) Jordan > > > Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message