Ratel wrote:
One such line says "Unknown word in configuration file"
Does this hold any kind of deep significance?
It says to me that the ISO you downloaded is corrupted.
When you execute
md5sum from the terminal and it didn't do anything means that the program is setting ther waiting. If you didn't have it, it would let you know. In retrospect it might have been more helpful to enter
md5sum --version, or
md5sum --help...but there ya' go.
Ok, so you have
md5sum...the next thing is to get it to find and check the file.
There are a couple or reasons why it's not finding it.
1) You are giving it the wrong path (directory(s)).
2) You are giving it the wrong file name.
3) There is a typo in the location or filename.
You will notice that those reasons are variations of the same idea. Computers aren't real good at fuzzy logic.
I don't type all that well. My proofreading is even worse. Sometimes I can't quite remember the spelling on a command or directory. There is a feature in the terminal I use quite frequently. This feature is "auto-completion". It should be enabled on your machine. You should be able to use it as well.
To use this auto-completion feature you hit the
<tab> key. It permits typing a partial command, then pressing the <Tab> key to auto-complete the command sequence.
If nothing happens; there are multiple possibilities and the computer needs additional information. Hitting <tab> again lists them all.
Or, or,...OR, you have given your computer the wrong lead and it can't find any possibilities available.
This is how it works:
Code:
wadda@example:~$ m<tab>
Nothing happens. But hit <tab> twice
Code:
wadda@example:~$ m<tab><tab>
Display all 324 possibilities? (y or n)
Too many options and/or you have an idea where you're going;
Code:
wadda@example:~$ md<tab><tab>
md5sum mdatopbm mdeltree mdu
md5sum.textutils mdel mdir
You see there are two listing that being with
md5. If you hit <tab> once it will auto-complete until there is a difference between possibilities....after that the computer needs additional input. Try it. Enter
md5. Hit
<tab>. It stops at
md5sum Hit
<tab> again and it lists the possibilities.
Code:
wadda@example:~$ md5sum
md5sum md5sum.textutils
If you are going in the wrong direction....
Code:
wadda@example:~$ md4<tab><tab><tab><tab><tab><tab><tab><tab><tab><tab><tab><tab><tab>
You can bang on the keys until they're bloody and nothing will happen.
So, let's make an assumption the file you want to check is in your
Downloads directory.
Enter:
md5sum /h<tab>
a<tab>
Dow<tab>
nav<tab>
Notice you've entered
Dow. This is because Downloads begins with an uppercase "D".
Desktop also begins with the letter
D. People also tend to have a directory
Documents which has
Do. Using the first three letter makes it a unique command and is then auto-completed. The same goes for the following
nav. Your looking for files that begin
nav. This includes the navigatrix.iso, but also incluses 'navigatrix[1].iso'; 'navigation.pdf'; 'navionics.doc'. But it excludes "nubian"; "namibia"; "nome"; "natural" ...or any other of the innumerable possibilities. It also excludes "Navigatrix.iso" because upper and lower case letters are different creatures.
If anywhere along the line <tab> does not auto-complete; or <tab><tab> does not list your options you are at the end of the line. Either you have the correct (intended) command, or you have a typo...usually in the form of an upper/lower case; missing letter (navgat...), or however we can mangle the command....or, and this is always a possibility; what you are trying to do; what you are looking for; is not there.
So you've entered the command, and thus far you have, e.g.,
wadda@example:~$md5sum /home/wadda/Downloads/navigatrix. If it stops <tab><tab> to list your options, and then type in the proper one tabbing when you can auto-complete you selection. Do it until you see the
.iso at the end.
Check the checksum....delete any file that doesn't match what it's suppose to be.
Give it a go.