2.6.5 bin files not marked as executable

[vgriffin]

Okay. I've just unzipped the bundled stuff onto my Linux box. I double clicked the run.sh in the bin directory. It opened the editor because it's not executable. In fact, the bin directory contains no executable files.

Obviously, I can figure out how to fix this, but I don't know which other files, possibly in other directories, might be permission-challenged and it shouldn't have been released this way....

[prabhat.jha]

You wont have to change permission of any other files.

[theute]

Come on....
"sh run.sh"

[vgriffin]

Double-clicking, as directed in Quickstart doesn't do sh run.sh