|No such thing as a small change|
Re^2: Shebang behavior with perlby afoken (Canon)
|on Mar 03, 2015 at 11:30 UTC||Need Help??|
Unix-shell programs are designed to read the first line of any “command file,” looking therein for a #!shebang™ line. If they find one, they fork() the specified command, providing “the rest of the input-file” to the subprocess.
I doubt that. In modern unixes, the shell simply fork()s and then wait()s, and, in the child process, invokes exec(script,arguments). The kernel, not the shell, detects what kind of file is about to be executed, and runs the proper loader/interpreter. For dynamically linked ELF binaries, the proper loader name is embedded in the ELF file (something like /lib/ld-linux.so). For other file formats, a similar logic is used. For some file formats, a hard-coded or configurable helper program is invoked. For scripts that start with #!, the interpreter is the first "word" (block of non-whitespace characters) after #!. It may have an optional argument (everything up to end of line).
Shells usually have some fallback code that handles a failing exec() for a text file, as required by POSIX.
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)