Why do you need to learn the command line anyway? Well, let me tell you a story. A few years ago we had a problem where I used to work. There was a shared drive on one of our file servers that kept getting full. I won't mention that this legacy operating system did not support user quotas; that's another story.
"Muito embora o Linux possua diversas e ótimas interfaces gráfica (GUI's - Graphical User Interfaces) bastante amigáveis, dentre as quais destacamos o Gnome e KDE , como de resto todos os sistemas operacionais Unix , ainda requerem por vezes que façamos uso da linha de comando. O ambiente tradicional do Unix é o CLI (Command Line Interface), onde você digita os comandos para dizer ao computador o que ele deve fazer. Esse modo é extremamente poderoso e rápido, porém implica que você saiba para que serve cada comando e seus diversos parâmetros.”
N namei Follow a pathname until a terminal point is found nano An enhanced free Pico clone nc arbitrary TCP and UDP connections and listens (note that nc is also called the client interface to the NEdit program but it is not the command that invokes nedit-nc on current systems) ncftp Browser program for the File Transfer Protocol nedit-nc nedit-nc is the client interface to the NEdit text editor netstat Display verbose info about network processes and ports nice Run a command with modified priority nisdomainname Show or set system's NIS/YP domain name nslookup query internet domain name servers
Shell scripts are short programs that are written in a shell programming language and interpreted by a shell process . They are extremely useful for automating tasks on Linux and other Unix-like operating systems . A shell is a program that provides the traditional, text-only user interface for Unix-like operating systems. Its primary function is to read commands (i.e., instructions) that are typed into a console (i.e., an all-text display mode) or terminal window (i.e., all-text mode window ) and then execute (i.e., run) them.