Date: Wed, 23 Mar 2011 20:39:27 +1100 From: Alex <other@ahhyes.net> To: <freebsd-emulation@freebsd.org> Subject: Re: linux app wont start... Message-ID: <00b25fc7c1edfdfa6cb43d7a9dda7c3e@ahhyes.net> In-Reply-To: <20110323095222.15512vskwxouiqkg@webmail.leidinger.net> References: <19271ad0af28730d9f735f955ec63db1@ahhyes.net> <20110323095222.15512vskwxouiqkg@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Here is the script: -------------------------------- [game@srv ~/bf2]$ cat start.sh #!/bin/sh MACH="" # 64-bit FreeBSD is "amd64"; emulates 32-bit Linux. case `uname -m` in i[3456]86 | amd64) MACH="ia-32" ;; x86_64) MACH="amd-64" ;; esac if ! [ -d pb ] then ln -s pb_$MACH pb fi BINARY_DIR="$(pwd)/bin" if [ -d "$BINARY_DIR/$MACH" ] then BINARY_DIR="$BINARY_DIR/$MACH" fi # Make the OS give us .core-dumps if the server crashes ulimit -c unlimited export LD_LIBRARY_PATH=$BINARY_DIR exec $BINARY_DIR/bf2 "$@" ------------------------------------- Looks like the freebsd one. So you're suggesting the linux one in /compat/bin ? On Wed, 23 Mar 2011 09:52:22 +0100, Alexander Leidinger wrote: > Quoting Alex <other@ahhyes.net> (from Wed, 23 Mar 2011 17:29:05 > +1100): > >> Hi Guys, >> >> I am trying to run a battlefield 2 server on FreeBSD 8.2 with linux >> emulation enabled, I have some other apps that run just fine. >> >> Here is the error I get: >> >> [game@srv ~/bf2]$ ./start.sh >> Error opening terminal: xterm. >> >> [game@srv ~/bf2]$ echo $TERM >> xterm >> >> I can "export TERM" and set another value but the result is always >> the same it will just say "Error opening terminal <whatever>" >> >> I have a suspicion it's to do with the termcap in the linux compat >> section, not the local freebsd termcap. > > IMO: There is not enough info to conclude this. > > It is not obvious which shell is used to execute start.sh (linux > shell or FreeBSD shell). To determine this we need to see the first > line of the script. I would expect a FreeBSD one is started and I > would suggest to try a linux one instead. > > Did you see any messages on the console (run "dmesg" after a failed > start and have a look for unusual output). > > I would also suggest to have "set -x" as the second line in the > script, this will give you a trace what is executed. The output needs > to be reviewed then to analyze what is going on. After a suspicious > action is tracked down, this action can maybe started within ktrace > and the linux_kdump port can then be used to further investigate what > is going on. > > Bye, > Alexander.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00b25fc7c1edfdfa6cb43d7a9dda7c3e>