I noticed some scripts are including a #!/bin/ksh shebang, is there any reason to use these limiters? It means that the scripts do not natively run on Mac OS X, or OSes that only have bash, sh, or other shells like zsh in archlinux, because the shebang will direct the script to a nonexistent script. Is there any functions there that require ksh? Or is it just a force of habit to shebang #!/bin/ksh?
I noticed some scripts are including a #!/bin/ksh shebang, is there any reason to use these limiters? It means that the scripts do not natively run on Mac OS X, or OSes that only have bash, sh, or other shells like zsh in archlinux, because the shebang will direct the script to a nonexistent script. Is there any functions there that require ksh? Or is it just a force of habit to shebang #!/bin/ksh?
Force of habit— I noticed it a while back, though, but didn't bother to change it.
We're all using these scripts on O/LBSD anyway, right, and not OSX? ;)
Force of habit— I noticed it a while back, though, but didn't bother to change it.
We're all using these scripts on O/LBSD anyway, right, and not OSX? ;)
I noticed some scripts are including a #!/bin/ksh shebang, is there any reason to use these limiters? It means that the scripts do not natively run on Mac OS X, or OSes that only have bash, sh, or other shells like zsh in archlinux, because the shebang will direct the script to a nonexistent script. Is there any functions there that require ksh? Or is it just a force of habit to shebang #!/bin/ksh?
Force of habit— I noticed it a while back, though, but didn't bother to change it.
We're all using these scripts on O/LBSD anyway, right, and not OSX? ;)