great video! Now, I do have a question. You mentioned that shells are only calling other programs to make them do their job, that I understand. But are commands like "cd" or "ls" included into the bash shell or those standalone programs as well?
In theory, anything "could" be built into a shell as a sub routine rather than as an external program. But with cd and ls, for example, on Linux use the "which" command to look up their path. Both of those commands exist as independent programs in the file system. So they are external. But some special shells, like BusyBox build them in.
So just to clarify, command prompt and terminal on windows and unix, respectively... these are command line interface, but they also run the shell such as bash which is the command line interpreter? But say when I run something like cd.., or mkdir, or cat, that application in itself is not part of the shell, but rather what the shell calls? Is that correct?
CMD is the name of the default classic Windows shell. Without a shell, you would see nothing. It is the shell itself that allows you to type commands. Windows Terminal is a shell "holder", it has to run CMD or PowerShell to do anything. But it can run either. The terminal provides the look and feel graphically, the shell is what takes any input and provides any output. Often tools like cd, cat or dir are built into the shell, but not always. Most things that you call, though, like top, grep, less, more, lsof, netstat, ping, and so forth are just applications that you are calling from the shell.
The outer layer analogy is confusing me a bit. Is it correct to think of a shell as a program that takes commands from a command line interface or GUI and forwards these commands to a software that has been programmed to receive this particular shells commands? May it be File Explorer, 3rd party software etc.
Thank you, there are so many awful videos on this topic on UA-cam. This actually explained it very clearly.
Thanks!
@@samit8178😮😮😮
This actually clears up some confusion I've had since I was a kid digging around with CMD.
awesome explanation!
EDIT (after having watched a few other videos): no bullshit-bingo, no buzzwords. You can tell he knows what he's talking about.
Thanks! Glad that it's helpful. This is what I love to do. :)
Incredible explanation. I'm surprised this video has only 6k views
Thanks Sam for the very helpful explanations of shell, I enjoyed as well
You are very welcome!
AWESOME MAN!!!!!
Term always confused me. Very well explained, ty!
You are so welcome!
doing the odin project, and they article they had linked explaining shells gave me a headache. this helped a ton
Thank you for this and level of detail that you went into to explain the term
Very well explained, it really clears the concept, thanks
Much respect to you bro. You broke it down very well
great video! Now, I do have a question. You mentioned that shells are only calling other programs to make them do their job, that I understand. But are commands like "cd" or "ls" included into the bash shell or those standalone programs as well?
In theory, anything "could" be built into a shell as a sub routine rather than as an external program. But with cd and ls, for example, on Linux use the "which" command to look up their path. Both of those commands exist as independent programs in the file system. So they are external. But some special shells, like BusyBox build them in.
So just to clarify, command prompt and terminal on windows and unix, respectively... these are command line interface, but they also run the shell such as bash which is the command line interpreter? But say when I run something like cd.., or mkdir, or cat, that application in itself is not part of the shell, but rather what the shell calls? Is that correct?
CMD is the name of the default classic Windows shell. Without a shell, you would see nothing. It is the shell itself that allows you to type commands. Windows Terminal is a shell "holder", it has to run CMD or PowerShell to do anything. But it can run either. The terminal provides the look and feel graphically, the shell is what takes any input and provides any output.
Often tools like cd, cat or dir are built into the shell, but not always. Most things that you call, though, like top, grep, less, more, lsof, netstat, ping, and so forth are just applications that you are calling from the shell.
thank you very much !!! great explanation
Very helpful video!
Great explanation, thanks
Glad it was helpful!
The outer layer analogy is confusing me a bit. Is it correct to think of a shell as a program that takes commands from a command line interface or GUI and forwards these commands to a software that has been programmed to receive this particular shells commands? May it be File Explorer, 3rd party software etc.
Thanks so much!
You're welcome!
Thanks a lot
Hello Please tell me Shell is a command interpreter?
That's correct. Either command line or graphic command interpreter for accessing the OS functions.
Did you just say that bash and KDE Plasma are both shells? You just changed they way I look at the world.
How do I install Bash? I downloaded a .sig file from www.gnu.org and have no idea where to go from here.
NM. found a way to use it via Windows 10. community.spiceworks.com/how_to/148352-how-to-install-bash-on-ubuntu-on-windows-in-windows-10
That's BASH on a VM, not on Windows. That will be completely misleading.
on point
Thanks!
Nice explanation about shell!
Thanks
Good explanation. Here is also a video that illustrates your point in a more technical fashion: ua-cam.com/video/EEvY9pptM5Q/v-deo.html