Where do I guet the tool to verify Md5Sum for PCLOS_2012 iso? Thanks for advise

[Loles]

Hi!

Where do I find the tool to verify Md5Sum for PCLOS_2012 iso?

I want to make a new butable live cd.

I can not find the info arround here, the first one i made was with Windows OS, but i want to make one in PCLOS LXDE with the original iso image dounloaded fresh from the oficial website.

Thanks for advise

[putz]

Loles,

It's built in.
In a terminal (PC / More Applications / Terminals) select either konsole or xterm.
Navigate to the place you saved the iso.
Type the command, "md5sum" (without the quotes) followed by the exact name with extension of the iso.
In a few moments, it will respond with the string which is the md5sum you can compare with the one from the download site.

Also, our burning software, k3b, does also compute the md5sum before you burn an iso.

Good luck,

putz

[T6]

that already having linux running, on windows there is a couple of free tools doing that exact action mentioned

this is one

http://download.cnet.com/MD5-Checker/3000-2092_4-10410639.html

another

http://www.exactfile.com/downloads/

another is md5summer but i don't know if still exist

[tschommer]

putz, the command is already installed: checkisomd5

If you have <filename>.iso and <filename>.md5sum, just enter

Code: [Select]

checkisomd5 <filename>.iso
Example:

Code: [Select]

checkisomd5 pclinuxos64-kde-test05.iso
It will check pclinuxos64-kde-test05.iso for the md5sum in pclinuxos64-kde-test05.md5sum.

[menotu]

Additionally, another way is to open Dolphin and go where md5sum check is to be carried out and press the F4 key which splits Dolphin in two with one half being the Terminal

[putz]

menotu,

Thanks for the tip about Dolhpin and F4.  That makes it convenient.  However, I was unsuccessful on trying it out on the pclinuxos64-lxde-rc1 iso.
It reported:
[rr@localhost data]$ checkisomd5 pclinuxos64-lxde-rc1.iso


No checksum information in iso, check skipped.
[rr@localhost data]$ checkisomd5 pclinuxos64-lxde-rc1.iso


The .md5sum file is in the same directory with the iso.  Did I do something wrong, or do not all iso's have the md5sun info included?

Thanks,

putz

[T6]

the md5 file is a number, that number is on the server where you downloaded the iso

in your particular case it should be this file

http://distrib-coffee.ipsl.jussieu.fr/pub/linux/pclinuxos/live-cd/pclinuxos64-lxde-rc1.md5sum

it is just a text file with this code in it

392b034fca4826a843c74800cd7eb66c

when you run any of the techniques to do a md5checksum and the result is equal to the number of the mde5 file you can verify that the iso is ok, didn't lost integrity in the download

[putz]

T6,  Yes I understand.  I've always run md5sum as in my first reply above from Konsole, gotten the number result and then opened the .md5sum file in Kwrite and compared the number to see if it was the same.  I just had tried Menotu's tip combined with tschommer's "checkisomd5" command.  However, I got nothing returned because it said, "No checksum information in iso, check skipped." 

What should have been returned from the command?

Since it said there was no checksum info in the iso, I asked if all .iso files should have the checksum information included, or did I do something wrong.

I like the F4 in Dolphin tip and will use it.

putz

[Old-Polack]

T6,  Yes I understand.  I've always run md5sum as in my first reply above from Konsole, gotten the number result and then opened the .md5sum file in Kwrite and compared the number to see if it was the same.  I just had tried Menotu's tip combined with tschommer's "checkisomd5" command.  However, I got nothing returned because it said, "No checksum information in iso, check skipped." 

What should have been returned from the command?

Since it said there was no checksum info in the iso, I asked if all .iso files should have the checksum information included, or did I do something wrong.

I like the F4 in Dolphin tip and will use it.

putz

Open the Dolphin terminal pane, navigate to the directory holding the .iso and .md5sum files you wish to check. In the terminal enter the command;

$ md5sum -c *md5*               <Enter>

[T6]

on the download site you can see the checksum file or value

since you are using a test iso the md5 is not posted, you have to search for it on the server where the iso is stored

afik, the iso doesn't have any md5 file in it, the md5 is a algorithm you run against a file and produces a result so there is no file inside the iso

maybe the app was expecting a file called pclinuxos64-lxde-rc1.md5sum together with the pclinuxos64-lxde-rc1.iso file?

op posted first 

[putz]

Ah Ha!  I think I see what happened.  OP's md5sum -c *md5* responded the iso was OK, but I also had the .md5sum file which I had originally downloaded from the server with the iso file to be able open with KWrite saved in the same directory with .txt on the end.  md5sum -c was put off by that .txt on the file name and reported it was not a proper md5sum.

All's well, and I picked up two nice tips;  1) F4 in Dolphin and 2) download both the iso and the .md5sum files into the same directory and issue "md5sum -c *md5* rather than download the iso and open the .md5sum file from the server in Kwrite then save it as a .txt file to open later and compare against what the command md5dum without the -c, etc. returns.

Now if my memory just holds up until the next time I need this stuff...

Thanks guys,

putz

[Phil]

My system is a combination of kget and awesum (both from synaptic)

With kget I paste in the link location to the iso, which then downloads it to a designated directory on my machine.

Whilst waiting I fire up awesum, paste in the md5 string off the website, and when ready it does the checking of the downloaded iso.

Then a slow burn with K3b.....(or for me usb drive with unetbootin)


Whatever system you prefer is right for you


ps You can also use Virtual Box to play with isos, assuming you have an ok system with plenty of ram. Look for getvirtualbox in synaptic and then run the install script. I tend to play with lighter distributions.

[Archie]

Ah Ha!  I think I see what happened.  OP's md5sum -c *md5* responded the iso was OK, but I also had the .md5sum file which I had originally downloaded from the server with the iso file to be able open with KWrite saved in the same directory with .txt on the end.  md5sum -c was put off by that .txt on the file name and reported it was not a proper md5sum.

All's well, and I picked up two nice tips;  1) F4 in Dolphin and 2) download both the iso and the .md5sum files into the same directory and issue "md5sum -c *md5* rather than download the iso and open the .md5sum file from the server in Kwrite then save it as a .txt file to open later and compare against what the command md5dum without the -c, etc. returns.

Now if my memory just holds up until the next time I need this stuff...

Thanks guys,

putz

If you have the ISO and md5sum on the same folder, an easy way to compare would be

md5sum name.iso && cat name.md5sum

And you can see if they are or not the same.