From owner-freebsd-questions Thu Feb 12 19:13:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05516 for freebsd-questions-outgoing; Thu, 12 Feb 1998 19:13:30 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from infowest.com (infowest.com [204.17.177.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05499 for ; Thu, 12 Feb 1998 19:12:48 -0800 (PST) (envelope-from agifford@infowest.com) Received: from infowest.com (gandalf.eq.net [207.49.60.254]) by infowest.com (8.8.5/8.8.5) with ESMTP id UAA27099 for ; Thu, 12 Feb 1998 20:12:45 -0700 (MST) Message-ID: <34E3BA0D.D885E8F5@infowest.com> Date: Fri, 13 Feb 1998 03:12:13 +0000 From: "Aaron D. Gifford" X-Mailer: Mozilla 4.03 [en] (X11; U; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: questions@FreeBSD.ORG Subject: Re: SCOM under BSD References: <3.0.1.32.19980212085024.00ddb0e8@frontier.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hehe, got a good chuckle from BSDI's response. FreeBSD can run BSDI binaries, but BSDI can't run FreeBSD binaries. Wonder why...Not! Couldn't be to force folks to buy their product in order to develop for it? ;) I'm not belittling BSDI. I quite like some of the things they've done, and in fact started out with their old BSD/OS 1.1 stuff before I heard of FreeBSD. It was rock solid (almost as solid as FreeBSD? ;) and I had an old Pentium 90 running a whole slew e-mail, FTP, & web accounts on it for 1.5+ years and the P90 never cracked a sweat. I'd see uptimes in excess of 6 months -- would have been longer were it not for forced reboots when I moved things around. This does make me wonder one thing: Is there any way to cross-compile for BDS/OS on FreeBSD, or is this just plain impossible? Has anyone tried? Aaron out. Kurt Raymond wrote: > > Hi Michael- > > Thanks for contacting us. > > BSDI and FreeBSD are not binary compatible. If you re-compile your > application under BSDI, that should do the trick. > > For more hints, check out the bsdi-users mailing list archive at > http://www.nexial.nl/cgi-bin/bsdi > > Best Regards, > > Kurt Raymond > BSDI > > At 07:02 AM 2/12/98 -0500, Michael J. Demerling wrote: > > > >We are developing a serial communications tool > >(www.sensorsoft.com/scomad.htm) for BSD. We compiled the program with GNU > >under FreeBSD Ver 2.2.1. > > > >The product works fine under FreeBSD. However it produces the following > >error message when run on a BSDI BSD/OS 3.0 server; > > > >Couldn't open /usr/libexec/ld.so. > > > >Any ideas why? We thought BSD products were inter-compatible. Can we easily > >make it compatible? > > > >Best Regards, > >Michael Demerling > >______________________________________________________________ > > > >Qtek > >912 Toll Rd., Mississauga, Ontario, Canada L4W 3W9 > >Phone: (905) 276-5556 Fax: (905) 276-4202 > >Email: info@sensorsoft.com Web: www.sensorsoft.com > > > >______________________________________________________________ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message