LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 09-25-2006, 04:14 PM   #1
buckdog
Member
 
Registered: Mar 2006
Distribution: Puppy, KnopMyth
Posts: 36

Rep: Reputation: 15
What's with the command line?


I am an uber-noob, but am wondering why doing so much stuff in linux uses the command line.

Thanks!
 
Old 09-25-2006, 04:18 PM   #2
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974
it gets stuff done quickly and easily once you are familiar with it. a 5 second console command can easily take minutes clicky here clicky there. and plenty of things can't be done at all.
 
Old 09-25-2006, 05:37 PM   #3
haertig
Senior Member
 
Registered: Nov 2004
Distribution: Debian, Ubuntu, LinuxMint, Slackware, SysrescueCD
Posts: 2,117

Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
A Windows-style GUI is good for leading you through a task that you don't really know how to do in the first place. Enough clicking, and you'll probably find what you need. You basically stumble onto it because you are familiar with the interface. This is good for things that you rarely do and need some guidance. It is also good for complex tasks involving graphics. I'm posting to this forum using Firefox - a GUI browser. And I can't imagine trying to remove the redeye from a photograph using commandline only.

If you know what you want to do, and how to do it, the command line is much more powerful and faster for many tasks. Requires a lot less of the system also (CPU, memory, etc.) This is good for the stuff where you don't need the hints and prods that a GUI can provide. Much of the stuff many of us do with Linux doesn't require a GUI, although under Linux you can find an optional GUI-wrapper for just about anything if that's what you want. K3B is a great example of a GUI-wrapper for the basic commandline stuff like mkisofs, cdrecord, growisofs, etc.
 
Old 09-25-2006, 07:28 PM   #4
pixellany
LQ Veteran
 
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Arch/XFCE
Posts: 17,802

Rep: Reputation: 738Reputation: 738Reputation: 738Reputation: 738Reputation: 738Reputation: 738Reputation: 738
In the beginning (Apple-II, commodore, DOS, etc.) we had nothing BUT the command-line. It is only in the last 10-15 years that people have come to believe that the GUI is the only way to run a computer.

In the better Linux Distros, most of what you need to do on a daily basis CAN be done in the GUI. But it is generally easier using the CLI.
 
Old 09-26-2006, 11:04 AM   #5
hand of fate
Member
 
Registered: Nov 2003
Distribution: Mandriva
Posts: 441

Rep: Reputation: 31
Quote:
Originally Posted by pixellany
But it is generally easier using the CLI.
I'm sure a lot of people would disagree with that statement!
 
Old 09-26-2006, 12:58 PM   #6
pixellany
LQ Veteran
 
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Arch/XFCE
Posts: 17,802

Rep: Reputation: 738Reputation: 738Reputation: 738Reputation: 738Reputation: 738Reputation: 738Reputation: 738
Quote:
Originally Posted by hand of fate
I'm sure a lot of people would disagree with that statement!
This is one of those things that are very dependent on how the question is asked....

If you are totally unfamiliar with the CLI, then it is harder to get something done.

If you spend ~ 4 hours learning a few basics, then certain things are easier at the CLI.

Here is an absurd example: Apple-II, circa 1980, proceedure to start the word processor:
1. turn on the computer
2. type "write" at the prompt

Show me any modern computer that will start up as quickly or reliably to do a specific task.
Show me a person who could not learn those two steps, but who CAN do a custom desktop configuration in a modern GUI environment.

We perceive as "easiest" that which we are most used to......
 
Old 09-26-2006, 01:34 PM   #7
extrasolar
Member
 
Registered: Feb 2004
Location: Northamptonshire, UK
Distribution: Windows XP, Arch Linux
Posts: 131

Rep: Reputation: 16
Quote:
Originally Posted by buckdog
I am an uber-noob, but am wondering why doing so much stuff in linux uses the command line.

Thanks!
Because that's what Linux is; you could ask the same question about MS-DOS.

Seeing as you're an "uber-noob" I believe you haven't fully grasped the concept of how Linux works. Given time, I guarantee that you'll be asking "Why is so much done using the GUI".

Enjoy Linux.
 
Old 09-26-2006, 01:37 PM   #8
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974
totally, and the other major factor is a learning curve. yes you need to know more to use a CLI than to use a GUI, but once you put in that initial groundwork you can very easily reach much higher levels of ability and convenience, all for the sake of eye candy.

And i'm not saying this is windows vs linux at all either. I come across so many areas of it where a product will present a web and console interface. in the first instance you play around here and there with the web interface to try things out, but time nad agin i gravitate back to the cli as i know and trust what is going on, and i can get the exact results i want a LOT fast, be it a linux box, a cisco switch, a packet shaper, and IDS appliance...
 
Old 09-26-2006, 01:45 PM   #9
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974
Quote:
Originally Posted by extrasolar
Because that's what Linux is; you could ask the same question about MS-DOS.

Seeing as you're an "uber-noob" I believe you haven't fully grasped the concept of how Linux works. Given time, I guarantee that you'll be asking "Why is so much done using the GUI".

Enjoy Linux.
Actually there is another angle here that may be being observed. as Linux is so different, and there are so many ways it can behave in the gui circle inparticular, it is not always a good environment for achieving a certain goal via documentation. I fscking hate KDE, i fscking hate debian. i am anot about to tell a debian/KDE user how to navigate their pointy clicky world that i don't know to achieve menial tasks. as long as you're not going too fasr into debians "twists" i can however tell you how to do that very simply here on LQ via a gui. which is easier to read...

1) right click the flashy thing in the task bar
2) select "wobble" from the menu
3) click the X to get rid of the annoying avatar
4) click the "squidge" tab
5) expand the tree and select the "flurp" option
6) click "report" (or "go" on some older versions - or "now" on version 32.2f)
7) complete

or

1) open a console
2) run "flibblety -abc"
3) complete

you mightn't understand the second as easily, but it'll sure as hell answer your problem and get you the answer you want.

this logic also applies heavily to software developers. they are all geeks, and so write installation guides at their own level, not least because the methods used at their level haven't changed in 10 years and work across nearly every system. there are bits and bobs in fedora or other things which only hang around for a single release, but then that's irrelevant for anyone not using fedora anyway.
 
Old 09-26-2006, 03:31 PM   #10
mrclisdue
Senior Member
 
Registered: Dec 2005
Distribution: Slackware -current, 14.1
Posts: 1,075

Rep: Reputation: 189Reputation: 189
I use Gnome, and there's always a terminal open.

To kill a running process:

GUI: System>Administration>System Monitor....wait for it to open....find the running process....highlight (or right-click)....end process....wait for it to end....oops, only root can terminate....um, now what?

CLI: su -; pwd; pidof process; kill -option pid ...next.


cheers,
 
Old 09-26-2006, 03:36 PM   #11
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974
Quote:
Originally Posted by mrclisdue
I use Gnome, and there's always a terminal open.

To kill a running process:

GUI: System>Administration>System Monitor....wait for it to open....find the running process....highlight (or right-click)....end process....wait for it to end....oops, only root can terminate....um, now what?

CLI: su -; pwd; pidof process; kill -option pid ...next.


cheers,
here's another one for you
Code:
man pkill
 
Old 09-26-2006, 06:25 PM   #12
haertig
Senior Member
 
Registered: Nov 2004
Distribution: Debian, Ubuntu, LinuxMint, Slackware, SysrescueCD
Posts: 2,117

Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
Quote:
Originally Posted by acid_kewpie
i am anot about to tell a debian/KDE user how to navigate their pointy clicky world
As a Debian user, my pointy-clicky world is pretty much limited to three icons in my Gnome panel - "New Terminal Window", "Firefox", and "Thunderbird". Of course I'll run other GUI programs, but not all that frequently.

---

Debian (or any distro) does not preclude CLI. If I want to create a new account, useradd is my choice. If I want the burn a CD/DVD, it's mkisofs/cdrecord/growisofs rather than K3B. A new startup script? vi /etc/init.d/xxx and manually symlink to the /etc/rcX.d directory I'm targeting. Just because Debian comes out of the box with "easier" ways does not mean anyone has to live and die by them.

But I can't imagine brain-bashing myself trying to browse LQ.org using only wget and vi from the command line. lynx would be better, but still a tad tedious!

You can use distros both ways - CLI or GUI, as you see fit (assuming X is installed). Which knowledge/experience do I value more? CLI. No doubt about it. I can use it anywhere ... it's not distro-specific (for the most part). It's no big deal to flip over to one of my Solaris accounts either. CLI is CLI, with only minor adjustments as you hop between *nix OS'es.
 
Old 09-26-2006, 06:41 PM   #13
jstephens84
Senior Member
 
Registered: Sep 2004
Location: Nashville
Distribution: Manjaro, RHEL, CentOS
Posts: 2,098

Rep: Reputation: 102Reputation: 102
Just my two cents but I think alot of sys admins find that mangement through cli is easier. Especially when the machine is say at another property or could just be a network server. It is easier to make a ssh connection to the server and run a couple of commands then to get up, walk to the server, find the right application, open it, and then do the same function.
 
Old 09-26-2006, 10:03 PM   #14
nflenz
Member
 
Registered: Feb 2006
Distribution: CRUX 2.4
Posts: 96

Rep: Reputation: 18
"The X server has to be the biggest program I've ever seen that doesn't do anything for you."
- Ken Thompson
 
Old 09-26-2006, 11:36 PM   #15
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 122Reputation: 122
And a lot of it has to do with developers as well... honestly, many developers are just too lazy to add a GUI... the CLI gets the job done for them, so why write a GUI? In many cases, a GUI would have more code than the code that does the work.

Also, some things just don't make sense in the GUI paradigm... take pipelined commands... in the GUI, it's hard to connect tools together to make the 'bigger' tool.
 
  


Reply

Tags
bash, command, gui, line, script


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Is there a single command to list all hardware installed (command line)? davee Linux - Hardware 6 02-28-2009 08:19 PM
Redirecting output to a command-line argument of another command madiyaan Linux - Newbie 1 02-19-2005 05:35 PM
Command to output file content line by line aznluvsmc Programming 2 09-12-2004 08:45 PM
51 characters only in the 1st Line of command line eggCover Linux - General 2 07-29-2004 02:28 PM
Command to display whole filestructure hierarchy f/ command line? mjewell Linux - Newbie 10 01-19-2004 11:48 AM


All times are GMT -5. The time now is 04:56 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration