*BSD News Article 38834


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!math.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!lerc.nasa.gov!purdue!mozo.cc.purdue.edu!staff.cc.purdue.edu!bj
From: bj@staff.cc.purdue.edu (Ben Jackson)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: Help!
Date: 4 Dec 1994 04:39:30 GMT
Organization: Purdue University
Lines: 26
Message-ID: <3brh62$kuu@mozo.cc.purdue.edu>
References: <3bpav0$23o8@tequesta.gate.net>
NNTP-Posting-Host: staff.cc.purdue.edu

In article <3bpav0$23o8@tequesta.gate.net>,
abc-miami <abcmiami@gate.net> wrote:
>I read that FreeBSD had the ability to run SCO binaries.... How?

If you make them executable (chmod a+rx) they should run like "regular"
binaries or shell scripts.

>I moved a copy of ksh from my SCO to my FreeBSD, and it said "invalid ("

That usually indicates that the binary is being fed to the shell
(probably by your shell and not the kernel).  You might want to try a
simple binary first, like a "Hello World" a.out and see what happens.

I should point out that ksh is NOT freely distributable, and your
license may not extend to running the binary on other systems or
platforms.  You should check into using pdksh as a replacement.

>Also, under X, the X -probeonly kills my display....

If your card isn't supported, the probes for other cards may set
registers in your card incorrectly.  Make sure you're using the right
X server binary and try specifying your chipset explicitly in your
XF86Config.

--
Ben Jackson