/bin/bash will be as well because /bin itself is a symlink to /usr/bin.
Though that’s a very dumb shebang to use and you should be ashamed: lots of systems don’t have it, or have an absolutely ancient system bash. By hard coding this you’re just making your scripts worse.
Where? POSIX says:
Applications should note that the standard PATH to the shell cannot be assumed to be either /bin/sh or /usr/bin/sh, and should be determined by interrogation of the PATH returned by getconf PATH, ensuring that the returned pathname is an absolute pathname and not a shell built-in.But the issue I’m talking about is using the specific path /bin/bash, as that just reduces compatibility compared to going through env.
the /usr/bin/env bash thing always just seemed like pointless cargo culting to me. never had this problem
“/usr/bin/env bash” will keep the shebang working between a Linux and FreeBSD (and probably other *NIX) machines. This bit me at one point, and it just became a habit since.
Bash (if installed) is in /usr/local/bin there. Other interpreters often are too.