Click here to Skip to main content
15,890,527 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
To understand this well, I would like to have very strong foundations that will work their way up. Some of my questions might appear foolish, but I am just seeking equanimity.


I am speaking as how you would define these words?
Posted
Updated 8-Dec-15 7:37am
v2
Comments
Richard MacCutchan 8-Dec-15 13:53pm    
A script is what actors read.
A shell is found on the beach.
Afzaal Ahmad Zeeshan 8-Dec-15 14:12pm    
Let's bash! :D
Sergey Alexandrovich Kryukov 8-Dec-15 14:26pm    
:-) :-) :-)

1 solution

To keep things simple, "script is the command that shell executes". In most of the Linux environments, terminal is just the name given to a shell interpreter. Shell interprets the commands, that you pass a script. Then executes them "in a blazing fast speed".

Most of the times, for example, you execute a command to install a package,
sudo apt-get install package-name

This is just the script. It has no meaning in any environment, but shell; the terminal. Shell would interpret the command, one by one. Then it would build a command to be executed. In this case, it is an "install the package". Shell script is sometimes also called BASH script.

Please read the following helpful resources to learn more on these topics.

http://askubuntu.com/questions/111144/are-terminal-and-shell-the-same[^]
http://superuser.com/questions/144666/what-is-the-difference-between-shell-console-and-terminal[^]
https://en.wikipedia.org/wiki/Bash_(Unix_shell)[^]
 
Share this answer
 
Comments
Member 12194229 8-Dec-15 13:58pm    
This is exactly what I was looking for. Thank you.
Sergey Alexandrovich Kryukov 8-Dec-15 14:34pm    
"It has no meaning in any environment, but shell" is quite inaccurate. Apparently, in any application, if you start some process by the name of the file "sudo" (which is usually also a script, by the way), and pass the rest as command line, the same process will be started. In this sense, the lines line the one in your example is something more than all of the shells, and is more general then the script. Perhaps you can make your post valid (and valuable) if you replace the example with something which is really written in one of the script engines.

It also good to explain that it's not exactly the shell which "interpret the command, one by one", it's a command interpreter. Python can be used for scripting, used interactively through the terminal (exactly as bash, csh and other), but you don't call Python "shell", right? You call it language and interpreter.

—SA

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900