vier986 wrote:A lot of posts say read,Read-But What.
to expand I think this is said so generally for because its ment in a couple of ways... (or at least that Is why I state it like that.)
First, and a little more optional... Read the manual, read a book, read the support forums, ect... Some will talk about how hard linux is, while others will assure you that anyone can do it. The truth is its not THAT hard, but you will be expected to learn and know more. Linux, especially in its younger days provided you with a working system to use...But kind of expects you to know what your doing. A lot of people have put a lot of work into programs and distros that are user friendly and intuitive... But it pales in comparison to commercial OS where an entire department poured piles of money at the software to make sure that not only could those who don't really know what they are doing make it work, but that it would work to for those who are basically offended by the notion that they would be expected to understand what they are doing in the first place. As easy as linux becomes, due to the nature of its development (normal people building you things for free) your probably always going to have to come a little closer to meeting the developer in the middle and learning some things yourself.
Secondly, and perhaps more importantly... Keep that head up and pay attention. Perhaps its the fault of so many years of windows bluescreens offering us "fault 0xA99994F3B" or what ever the hell it is. Perhaps its so many years of being coddled and expecting customer service to fix it. Perhaps its just learned behavior of the way it is done in the windows world... But don't just say "Ohhh, I got an error so it does not work."
So many newbie help requests because the lines they copied and pasted "Didn't work because they had an error".
"What did that error say?"
"I don't know I closed it. Why wont my program work?"
When there are popups, or error messages READ. You may not understand everything, but I CANNOT TELL YOU how often people blindly follow directions, then come and complain it doesn't work. When asked for a log of the terminal messages, its clear they downloaded a file with a version number, say "some-file-V1.2.5.tar" when the directions were written for "some-file-V1.2.4.tar". That alone is not necessarily a big deal, but you will see them post a log that looks something like
*first they post a link to the file some-file-V1.2.5 they downloaded*
- Code: Select all
$: tar -xvf some-file-V1.2.4
tar: some-file-V1.2.4: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
$: cd some-file-1.2.4
bash: cd: some-file-1.2.4: No such file or directory
bash: ./configure: No such file or directory
make: *** No targets specified and no makefile found. Stop.
"Teh tutorial didn't work! HELPZ!"
So often people just go "OH THERE WHERE ERROR MESSAGES! IT DOESN'T WORK! LINUX IS TERRIBLE AT COMPUTER!"
Now part of this goes back to point 1. If you have ready some stuff you know that tar is a program to unzip, and the .tar.gz package is compressed and should give us a folder of stuff if we do this right.
VERY QUICKLY we should see the errors started with our first command.
Paying more attention we can see the first command could not find a file, even though we just downloaded one... What did you download and why didn't it work (at that point you should be able to see you are using a command with a different file name. Seem simple? Yup. Sometimes the output will be longer, but taken one command at a time... whats the difference?
We see the errors continue on each line, indeed this is a huge mess and EVERYTHING FAILED! flail your arms, cry on the floor and run for your wallet to purchase 3 new copies of the latest microsoft offering...
Or actually READ each error and see that the second command tried to enter the folder created by decompressing the tarball in the first step... OF COURSE THIS WILL FAIL. Each command then there after should be expected to fail as we didn't even get the directory we were supposed to be issuing the subsequent commands in set up.
This is an easyish example, and again some formal knowledge would really help but more then anything don't look at error messages as something to be dissmissed to quickly. Read them at a minimum, copy them down if need be and try to at least get the jist of what is complaining. If you don't know what the utility is that is issuing the error, look it up on google. You don't have to have a mastery on every thing given to you but pay attention to what step complained about what and see if at least some of the words don't make sense to you... then give a quick google, look through man pages and copy and paste the generic part of the error, starting at the begining. The first error we saw was
"tar: some-file-V1.2.4: Cannot open: No such file or directory"
So lets google search
"tar: Cannot open: No such file or directory"https://www.google.com/search?q=tar%3A+ ... 2&ie=UTF-8
No quotes on the actual search, because I omitted the file name and just want something to match that general output...
Reading the first couple of results shows some forum discussions reminding us that the file we are running tar on needs to exist and we need to own it or have rights to mess with it.
On the commands you are issuing, and the errors they are giving.