Run the installer? You mean like this?

[Reticent]

Like in 'buntu, where "bash" means run-a-shell-script, open a terminal where I unpack pminstaller.sh and then run

Code: Select all

sudo bash pminstaller.sh

(I didn't see an example on the SourceForge wiki ...)

[access2godzilla]

You can run it in many ways:
- With most file managers, you can double click it.
- From the terminal, use "./pminstaller.sh" (the script will automatically elevate with the help of sudo.)
- With sudo, use "sudo ./pminstaller.sh" (your method does work in this case, but it's not preferable to do that everywhere).
- If you don't have sudo (or not allowed to run it) use "su -c ./pminstaller.sh".

BTW, bash != run a shell script, it means run the bash shell (there are others like sh, ash, zsh, csh and korn). bash foo.sh means run a shell script in bash, overriding the preference of the shell the script wants to use.

[Conan Kudo]

Most shell scripts would override the shell using the shebang clause at the beginning of the script though, wouldn't it? Ordinarily, the user need not manually override the used shell.

[access2godzilla]

Not actually overridden -- when a shell script, marked as executable is invoked like a program, the program specified on the #! line is invoked with the path of the shell script as its argument.

When a shell script is invoked with <shellname> <filename> through the shell, the #! line is specially treated (usually as a comment, most shells as well as python etc. but as an ignored preprocessor directive as in the case of Bellard's tcc.)