Quote:
Originally Posted by sydmalicious
The chmod command no longer works with this version of Kindle for Mac, 1.20.3. Just tried it. Fails.
|
What's the ownership and permissions on the file before and after?
i.e. what's the output of
Code:
ls -l /Applications/Kindle.app/Contents/MacOS/renderer-test
also while we're at it
Code:
file /Applications/Kindle.app/Contents/MacOS/renderer-test
Seems like the goal is to block execution of this file. If the chmod -x no longer does that it could be because it's being added back before execution. Another alternative is that the file isn't a binary - to execute a shell script you only need read permission. The file command would answer what type of file it is.
Now that I think of it, if the goal is to block execution and for K4Mac to see it's failed and therefore not use KFX then all you need is for renderer-test to always fail. Try this:
Code:
mv /Applications/Kindle.app/Contents/MacOS/renderer-test /Applications/Kindle.app/Contents/MacOS/renderer-test.orig
ln -s `which false` /Applications/Kindle.app/Contents/MacOS/renderer-test
That is rename the file and replace it with a link to the false executable (it's usually /bin/false but I wasn't sure on MacOS hence the backtick command)