Re: shrike-i386-disc 2 problem

[John Haxby <jch samsungcontact com>]

The command you run is

   md5sum shrike-i386-disc2.iso

where "shirke-i386-disc2.iso" is the name of the file that you want to 
find the MD5 checksum of.    If you're having difficulty doing this you 
need to find someone close to you who can help -- I'm afraid this is a 
bit to basic to be able to help much in a mail message.

jch


ivan Zbiral wrote:

> I have looked at the file size and it is ok. I dont understand the way
> of checking md5sum would you mind telling me the "step by step
> guide"....I feel stupid to ask for this but according to guide on REDhat
> website i should run md5sum from command line ...if I do this in windows
> it doesnt do anything. Now you are telling me that it should run under
> linux or cqwin utility?
> what I did initially was I went to directory with al my iso files and
> through win cmd line I typed md5sum (and the file namme of the image)
> ....but this doesnt do anything
>
> thanx for any replies
> ivan
> ----- Original Message -----
> From: John Haxby <jch samsungcontact com>
> To: <shrike-list redhat com>
> Sent: Monday, June 30, 2003 2:36 PM
> Subject: Re: shrike-i386-disc 2 problem
>
>
>  
>
> > It's going to be much easier to check the ISO image first:
> >
> >    md5sum shrike-i386-disc2.iso
> >
> > (or whatever it's called).   The MD5 checksums for the CDs are:
> >
> > 400c7fb292c73b793fb722532abd09ad  shrike-i386-disc1.iso
> > 6b8ba42f56b397d536826c78c9679c0a  shrike-i386-disc2.iso
> > af38ac4316ba20df2dec5f990913396d  shrike-i386-disc3.iso
> > 0727c51ab359dafa9ab31e0c50958aa6  shrike-SRPMS-disc1.iso
> > 2ddd8e6a8502869cd2e78d47590b9be1  shrike-SRPMS-disc2.iso
> > f378cf68b22c3b9a64c86b5067511630  shrike-SRPMS-disc3.iso
> >
> > (the MD5SUM file in the download area contains this lot).   You can
> > check all of the images in one go by doing:
> >
> >    md5sum --check MD5SUM
> >
> > Of course, to do all this one needs a Linux box.   Or you can download
> > and install "cygwin" (you can get that from www.redhat.com as well --
> > just search for "cygwin").   If you can't check checksums for some
> > reason then just look at the file sizes -- corruption normally comes
> > from truncated files rather than actually damaged ones.
> >
> > jch
> >
> >
> >
> >    
>
>
>