We can now create and execute a simple script, but we need to consider the name a little. In this case, hello1.sh will be good enough and is unlikely to clash with anything else on the system. We should avoid using names that may clash with existing aliases, functions, keywords, and building commands, as well as avoiding names of programs already in use.
Adding the sh suffix to the file does not guarantee the name will be unique, but, in Linux, where we do not use file extensions, the suffix is part of the filename. This helps you to provide a unique identity to your script. Additionally, the suffix is used by the editor to help you identify the file for syntax highlighting. If you recall, we specifically added the syntax highlighting file sh.nanorc to the nano text editor. Each of these files is specific to a suffix and subsequent language.
Referring back to the command hierarchy within this chapter, we can use a type to determine the location and type of file hello.sh:
$ type hello1.sh #To determine the type and path $ type -a hello1.sh #To print all commands found if the name is NOT unique $ type -t hello1.sh ~To print the simple type of the command
These commands and output can be seen in the following screenshot:
