Re: Command not found while trying to install a .run file
"I installed it on a Windows partition..." says it all.
Windows filesystems have no concept of execute permission. You can fake it with a mount option like umask=000 (which gives anyone permission to read/write/execute anything), however, then you have to be careful about accidentally executing something that should not be executed. By doing that I was able to run quake3 from a FAT32 USB memory stick on a Raspberry Pi (which runs an arm version of Debian wheezy Linux).
Another thing that can trip you up is that DOS/Windows uses different line endings (carriage return, linefeed) than *nix systems like Linux (linefeed only, also called newline). So if you edit a script in Windows, or something like ftp automatically switches line endings in text files, scripts may not execute, but the error can be confusing.
For example if attempting to run a script tries to print an error about "/bin/sh^M" not found, the Ctrl+M in Linux returns to the start of the line and the rest of the error message overwrites that (ie, you only see part of the error).
I am guessing that the reason for the unterminated quoted string error when trying to use sh to run it is that something uses back slashes to continue lines, but instead of escaping the newlines, it escapes the invisible carriage returns, and the line ends with an actual newline before a closing quote. Either that or something word wrapped during editing.
So it is usually best to stick to Linux file systems for running Linux scripts, tools for editing them, or running Linux binaries.
Last edited by efflandt; January 8th, 2013 at 07:55 AM.
i5 650 3.2 GHz, 8 GB, nvidia GTX 550 Ti @ 1080p (year old GT 430 began freezing) and assorted other computers