Open a terminal window in whichever version of Linux you are running and type
pwd. This stands for 'print working directory', and the response you get will look something like this:
This tells you that your current directory is called
user, and is one level beneath the
home directory, which is immediately off the topmost, 'root' directory, represented by the initial
/. To get to a new directory we use the
cd command we touched on last time, which stands for 'change directory', just as it does under DOS. To show the contents of the current working directory type
ls, which is shorthand for 'list'.
These commands - carried over from the original Unix on which Linux is modelled - are all characterised by brevity. Back in the day when you were having to enter all your commands from the keyboard there was an advantage to using as few keystrokes as possible. The GUI is often seen as a welcome release from this drudgery. But old hands - like Dave the Fingers - would point out that mouse excursions over the GUI can often be much more time and energy consuming, particularly when it sends you delving through layers of dialogue boxes, negotiating tabs and ticking boxes. A single command line incantation - assuming you know and can remember what it is - may get the same job done more quickly and more effectively.
But how did those old Unix guys remember all those esoteric commands? The answer:
man. This three-letter command, standing for 'manual pages' gives the user systematic access to information about all the command-line operations, including the usually bewildering variety of parameters these commands accept.
Both SuSE Linux, supplied with the Wind, and the Xandros distro that comes with the Eee PC provide the
man pages facility. Alas, it's missing from the AA1 . But that's very easily remedied. Last time, we saw how the
yum package manager can be used to show what software is available on the machine and what can be added. It's not safe to add everything on the list, but let's see how we get on with the
Unix as Literature
Command line-averse users might do worse than read Thomas Scoville's article Unix as Literature here. It may not convert mouse-pushers, but it will at least give them some idea of where the key-tappers are coming from.
where did you pull that from? It's far more than 2%.
Munich government, Venezuela, OLPC, Africa, Europe and lots of other places use a LOT of Linux. Look at the top 500 fastest computers. Lots of Linux.
Linux netbooks sell out. XP netbooks sit on the shelves. Each one means your 2% is wrong.
You can't bit me. Either "bite me" or "bid me". Depends on what you think you're doing.
Oh yeah - all those reasons are why Linux has barely a 2% market penetration.
Your comment about OEMs make me chuckle. You obviously have no clue about how business works. An OEM can only sell what people demand, and the people are not demanding user-hostile and incompatible OSs. They want Windows because that lets them get their stuff done.
The fact you do not care and your descent into vulgar language is indicative of the entire FOSS ethos IME. So long as the geeks are OK, who cares about ease-of-use for the end-user or productivity? This is why Linux is lagging behind Windows (and OS X) in just about everything.
If you want industry grade tools, you need to get the professionals in; not the weekend hobbyists.
I bit you good day and I will not return to this debate. I have no desire to be subject to more abuse and vitriol from the likes of you.
clear link to part one
Could you please add a link to the first part at the beginning or end of the article.
(I had to go back after reading through and find the link within the article itself, but an additional one would make it much easier to keep up with the series. It'll help once there are more than two parts as well.)
....and I thought these comments were moderated? Is that purely based on swearing/spam/porn then? The petty flame war that's going on here put me off reading what was left.