Usually to get a program run with bash (which you seem to be running), you do these things:
- make sure the file is chmod'ed executable using
- just run it; typing file.x
may not (read: usually won't) run the file, because the directory isn't probably listed in the $PATH environment variable and those directories listed there are the ones where bash looks for the given command. Running works either using a full path or shortening it with the dot-file method:
the latter works, of course, only if the file is in the current working directory. With full path the file should run, if it's just chmod'ed executable first (only needed once). One more thing that might affect is if the place where the file resides isn't marked executable (for example if the filesystem is mounted with the noexec
option, executables can't be run afaik; could be for directories too).