Author Topic: "cannot execute binary file"  (Read 3749 times)

Zargoon

  • Wayfarer
  • *
  • Posts: 3
    • View Profile
Re: "cannot execute binary file"
« Reply #15 on: April 09, 2007, 01:19:26 am »
Doing a chmod 744 planeshiftfile.bin  did the trick.  Must be different on Suse.

bilbous

  • Guest
Re: "cannot execute binary file"
« Reply #16 on: April 09, 2007, 03:33:41 pm »
Each flavor of Linux has it idiosyncrasies. Ubuntu, if it hasn't changed since I last looked at it comes with either no root password or an undisclosed default root password, their idea being the first user is a sudoer. I never liked this so the first thing I always did in a new Ubuntu was
Code: [Select]
sudo passwd root so that I could su root and my root password would be mine only.
Some distributions may require you to execute binaries using sh others do not, the use of the ./ is generally required because the folder may not be in the execution path, it is a short form for "the current directory" so if you are not currently in the directory where the program was downloaded it will not run. You can instead refer to it by the full path and your command might look like
Code: [Select]
sh /home/Geckus/download/Plane* Of course using the wildcard may be undesirable in the event you have more than one Plane.... files.

I personally like to install the game as root and then assign the games ownership to my user:group during the install. If you are not installing as root check the ownership of the download if it does not belong to your user you may have to chown it. I am not sure about this games download but I have had other downloads which retained ownership by users not on my system. This is typically a problem when compression software is used and it decompresses with the original ownerships. I do not think this is the case with the PS binary though.

crashedata

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
    • Crashedata Internet Radio
Re: "cannot execute binary file"
« Reply #17 on: May 05, 2007, 09:33:15 am »
I had the same problem, however when I typed chmod a+x instead of chmod +x, i got it working.
~"Legends are nothing but fiction. Some one tells it, someone remembers it, everyone passes it on" - Solid Snake -- Metal Gear Solid 2: Sons Of Liberty ~