It's a common security precaution to mount /tmp noexec to avoid running potentially unpleasant binaries. The 64bit linux installer script (I don't know about 32 bit, but I assume it is affected as well) decompresses to the /tmp filesystem and then runs setup.sh. This does not work for those who have /tmp mounted noexec, which prevents the installer from working (with a rather cryptic message of "/bin/sh: bad interpreter". If you experience this problem, edit the installer .sh file and change the temporary directory to a filesystem other than /tmp.

To fix this, the installer could check for noexec and choose a different location or at least provide a useful error message.

If you have a shell script on /tmp, mounted noexec, and you /bin/sh /tmp/blah.sh does that work?

The installer is just a simple makeself script, so it will accept a --target <dir> commandline argument to extract elsewhere. I could generate the scripts with --notemp, which will extract to the CWD instead by default. That might be better overall; then I could just mv the files and it will probably already be on the correct filesystem. (It is pretty dumb overall though to extract to /tmp and then copy it to its destination.. it's like downloading in Internet Explorer.) Yeah, I think I'll do that.

The loki setup installer also uses makeself, I think, and it looks like it has a few patches above and beyond the vanilla makeself. I was considering switching to that.