Jonathan, Thanx for your help. I appreciate that you have taken the time to explain it to me. However as I still haven't achieved a breakthrough.
> Make sure that the file is executable by typing: > >chmod +x fgfs_... > Yes, I did that. (It was +X in the man) >When you run the file, do it via: > >./fgfs_... --fgroot=/fully/qualified/path/to/base/packages So I still need to know: Is typing ./fgfs-0.8.0-09.10.02 --fgroot=... at the prompt supposed to execute the program? Isn't there some command like "run" or "execute"? Is the program supposed to be executable from the Finder? Is the ./ necessary if your working directory is where the executable is? Is "/fully/qualified/path/to/base/packages" suposed to start from the root directory, the home directory, or can it be from the current working directory? Which in this case is the same level as the fgfs application. I tried just typing ./fgfs-0.8.0-09.10.02 --fgroot=/path/to/base/packages in any number of forms and get either "Command not found" or "Permission denied" errors. I know I'm asking stupid questions, but I'm a Mac user and I've never executed a program from UNIX before. Thanx for your indulgence. Ken Spiker > >The path to the base packages can be found by changing into the directory >and typiing pwd (print working directory). If you don't want to always >add arguments to the command line, you can create a file called .fgfsrc in >your home directory. MacOS X will hide this file from you in the finder, >so I make a link to it that MacOS X can find (ln -s .fgfsrc _fgfsrc). Put >one command line argument on each line, and no not use any trailing >spaces. This file will be loaded when FlightGear starts. > _______________________________________________ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users
