A Beginner's Guide to the Linux Command Line

[infiltrator]

Linux command line: Powerful but painful. Just my opinion.

The Linux terminal is very powerful in deed, but it does take time to learn it, that's why its so painful. I don't call myself an expert, but I am still learning the commands. You have to start from somewhere, and then advance from there.

 

[VitalyT]

The thing about Linux that pisses me off most, is not the need for all the commands, it's that when I have to use it once a year I forget most of the commands again and have to re-learn them. That alone is an incentive to never touch Linux, not even once a year.

 

[DelJo63]

Linux Desktop has a GUI and like Windows or Mac, you seldom need the Command Line interface - - that is far more useful for the Linux Server

 

[Mr Mister]

I remember when I first used Linux. It was Debian earlier stages, no UI just line and a keyboard. Lol.

 

[ArtBa]

The CLI was swapped in favor of the GUI. With a GUI though your limited to what is presented to you. With a CLI it's much more dynamic allowing for some powerful commands. Microsoft have even jumped on this with their addition of PowerShell. Obviously a CLI is not as user friendly so naturally guides like this exist. This guide is very well written.

I agree. What GUI users don't understand is that in the "real world", many operations are scripted and are run as batch jobs. You can't do that from the GUI. So, for all those who complain about the arcane nature of the command line, you don't have to use it for trivial things.

 

[ffej02]

I prefer the Linux command line over the microsnooze and it's powershell...any day of the year.

Linux is consistent over the years, and you're able to change from one flavor to another flavor and still able to work. With only a little difference in commands from Redhat to Debian OS's. And maybe some file locations.

Powershell ...your're left wondering what version of the OS will work with what server version. Oh wait! Seven is not compatible with 2012r2 ....find a Windoze 8 or 10 computer. Or set up a VM and waste yet another 4GB of ram 2016r2 is only compatible with Windoze 10......more money for a OS or 4GB more of ram on a VM. Windoze 7 is not supported anymore......WHAT !!!!

What commands worked in 2008r2 ......won't work in 2016r2. Time to bridge that learning curve. GREAT !!!!

1400 yum or apt-get updates on a fresh Linux install with 1GB of Ram and 1 processor..... Maybe 30-40 minutes.

Windoze Server 2012r2 .... at 10GB of Ram with 4 processors ....waiting...waiting....waiting. Drive home....log in .....waiting. for a whole 134 updates on a fresh install of 2012r2. WIth NO AD installed....NO DNS installed. NO DHCP installed........Seriously !

I won't even get into Remote access on Windoze vs Linux SSH setup. Hands down SSH wins.

ACK!!!!!! STOP THE WORLD FROM SPINNING IN BILL GATES WORLD !! I wanna get off of it.

 

[wendy walsh]

The command line is useful for some things, but what I'd really like to see is an article about obtaining drivers, specifically USB drivers for things like WiFi adapters.

 

[Davit Sassuntsi]

Every computing enthusiast should get an understanding of the commands presented (as they're now applicable to all OSs, including Windows).

Should every driver get an understanding of how to rebuild an engine or the car's transmission, too? No. Should everybody learn to make their own soap? No. Why not? Because there's no pressing need to do so. People have better things to do with their time.

You Linux guys still don't get it, do you? How many years will it take?

 

[Raoul Duke]

Even I, yes, even I use the Windows Command Prompt. Sometimes it's just faster and easier. Chkdsk all the drives, when I install new drives, initializing and partitioning them etc, just easier than a zillion windows. Don't even have to move your hand from the normal typing position on the keyboard.
and of course their is more, so very much more. But if you just want to check out Facebook and stoke it to some porn maybe not so useful

 

[D3z4R1]

Great article! Thank-you.
It reminds me of when I was dabbling and playing around with Slackware Linux 2.5.

 

[batsdude]

To avoid using the <sudo> (NO < > brackets, of course) command when having to run multiple command lines, I just 'shortcut' the procedure by typing <su>(super user) and enter my pw. It alleviates having to enter the pw with everything you are running every time you enter a new command. That can get tedious, but having to run a pw with updating, changing content, etc, both in the cmd shell, as well as out, is also part of what makes Linux so much more secure than any other os. When you are done with the cmd shell, just close it, and the <su> entry is system relocked automatically.

 

[amghwk]

Haven't I seen this article before, here?

If it's a repeat, would it be helpful to puts foreword that this Isabel update or rehash of a previous article, citing the original date of the article?

Just a suggestion.

 

[Mugsy]

Nice article. Here are a some other things that may be worth knowing:
Linux is case sensitive, so /home/Name is different from /home/name
ls -l show long listing format

Quick correction: "ls" is "List Short". "ll" (LL) is to list the directory in "long" format.

The "less" command in Linux is the same as "more" in DOS. Smarter name, but inconsistency is confusing.

 

[Matt12345170]

Quick correction: "ls" is "List Short". "ll" (LL) is to list the directory in "long" format.

Think you might have been using your alias for too long.

 

[DelJo63]

Quick correction: "ls" is "List Short". "ll" (LL) is to list the directory in "long" format.

Review the MAN PAGE:

LS(1) User Commands LS(1)

NAME
ls - list directory contents

SYNOPSIS
ls [OPTION]... [FILE]...

DESCRIPTION
List information about the FILEs (the current directory by default).
Sort entries alphabetically if none of -cftuvSUX nor --sort is speci‐
fied.​

also

$ which ls
/usr/bin/ls
​

ls is a binary utility command

 

[Kibaruk]

To avoid using the <sudo> (NO < > brackets, of course) command when having to run multiple command lines, I just 'shortcut' the procedure by typing <su>(super user) and enter my pw.

While this does save you the typing of Sudo each time, -in my head at least- it defeats the whole purpose of actually having to use Sudo for security purposes.

Powershell ...your're left wondering what version of the OS will work with what server version. Oh wait! Seven is not compatible with 2012r2 ....find a Windoze 8 or 10 computer. Or set up a VM and waste yet another 4GB of ram 2016r2 is only compatible with Windoze 10......more money for a OS or 4GB more of ram on a VM. Windoze 7 is not supported anymore......WHAT !!!!

Oh boy, a linux fanboy who forgets how many distros and how much things actually vary from one to the other, including cli commands... yet remembers how many Windows -and can count with both hands together, maybe even smart enough and could use a single hand- versions there are and are actually being used.

 

[DelJo63]

It's just amazing how little understanding and ignorance it takes to subvert security and good control.

 

[fktech]

Nice article thanks.

 

[MikeOD]

Dumb as a fencepost article. Just as an example, if you type su <enter>, the you have auto management control, and do not have to type "sudo" ever again. Just plain dumb.

 

[woofer]

The command line is useful for some things, but what I'd really like to see is an article about obtaining drivers, specifically USB drivers for things like WiFi adapters.

Try this:
https://duckduckgo.com/?q=linux+usb+wifi+driver&t=h_&ia=web

Any reason to look for that in an article with this one's title?

 

[woofer]

Every computing enthusiast should get an understanding of the commands presented (as they're now applicable to all OSs, including Windows).

Should every driver get an understanding of how to rebuild an engine or the car's transmission, too? No. Should everybody learn to make their own soap? No. Why not? Because there's no pressing need to do so. People have better things to do with their time.

You Linux guys still don't get it, do you? How many years will it take?

An "enthusiast" is not the same category as "typical end user", so this article is quite appropriate for the former. There are plenty of articles to be found for using Linux GUI's for the latter.

 

[woofer]

The thing about Linux that pisses me off most, is not the need for all the commands, it's that when I have to use it once a year I forget most of the commands again and have to re-learn them. That alone is an incentive to never touch Linux, not even once a year.

That could apply equally well to using PowerShell in Windows...

 

[VitalyT]

That could apply equally well to using PowerShell in Windows...

Yeah, and I don't use that one either. I've learned to compromise with the Bash Command under Windows, so I can get the best of Windows + Linux in a simplified form.

 

[MaestroIT]

So this article confirms I am not a beginner: I knew all the commands listed and much more

 

[JStacts]

Should every driver get an understanding of how to rebuild an engine or the car's transmission, too? No. Should everybody learn to make their own soap? No. Why not? Because there's no pressing need to do so. People have better things to do with their time.

You Linux guys still don't get it, do you? How many years will it take?

No, but they should learn what "Park" does and how the emergency brake works. They should learn how to measure the life left in their tires. They should learn how to check their oil and tire pressure. They should learn how to correct an oversteer situation.