Difference between revisions of "Scripts on Linux"
Chris Tyler (talk | contribs) |
Chris Tyler (talk | contribs) |
||
| Line 3: | Line 3: | ||
When an attempt is made to execute a file, the kernel will check the file [[Linux Permissions|permissions]]. If the effective user has permission to execute the file, it will be opened and the first few bytes examined for a 'magic number', which will identify the type of executable. If no magic number is found, and the file is a text file, it will be interpreted by the current shell (identified by the SHELL environment variable). | When an attempt is made to execute a file, the kernel will check the file [[Linux Permissions|permissions]]. If the effective user has permission to execute the file, it will be opened and the first few bytes examined for a 'magic number', which will identify the type of executable. If no magic number is found, and the file is a text file, it will be interpreted by the current shell (identified by the SHELL environment variable). | ||
| − | If the first two characters of the file are "#!" (which is considered a magic number), then the rest of the first line of the file is used as the absolute path and arguments for the interpreter. This is called a "shbang" line, from "#" (sharp) and "!" (bang). Therefore, using this as the first line of | + | If the first two characters of the file are "#!" (which is considered a magic number), then the rest of the first line of the file is used as the absolute path and arguments for the interpreter. This is called a "shbang" line, from "#" (sharp) and "!" (bang). Therefore, using this as the first line of a [[BASH]] script: |
#!/bin/bash | #!/bin/bash | ||
| − | + | For a Perl script, use: | |
| + | |||
| + | #!/usr/bin/perl | ||
| + | |||
| + | This force the kernel to execute the appropriate interpreter for the script regardless of the current shell. | ||
There are three requirements for a valid [[BASH]] script: | There are three requirements for a valid [[BASH]] script: | ||
| Line 14: | Line 18: | ||
# The rest of the file must contain [[BASH]] commands. | # The rest of the file must contain [[BASH]] commands. | ||
# The file must be made executable (see [[Linux Permissions]]). | # The file must be made executable (see [[Linux Permissions]]). | ||
| + | |||
| + | [[Category:Linux]] | ||
Revision as of 22:43, 15 September 2008
Linux kernels do not use file extensions such as .bat or .exe to identify the type of content in files (although some Linux applications may do so). Instead, a Linux system examines the file contents and permissions.
When an attempt is made to execute a file, the kernel will check the file permissions. If the effective user has permission to execute the file, it will be opened and the first few bytes examined for a 'magic number', which will identify the type of executable. If no magic number is found, and the file is a text file, it will be interpreted by the current shell (identified by the SHELL environment variable).
If the first two characters of the file are "#!" (which is considered a magic number), then the rest of the first line of the file is used as the absolute path and arguments for the interpreter. This is called a "shbang" line, from "#" (sharp) and "!" (bang). Therefore, using this as the first line of a BASH script:
#!/bin/bash
For a Perl script, use:
#!/usr/bin/perl
This force the kernel to execute the appropriate interpreter for the script regardless of the current shell.
There are three requirements for a valid BASH script:
- The first line of the script must be
#!/bin/bash - The rest of the file must contain BASH commands.
- The file must be made executable (see Linux Permissions).
