Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 12 Oct 2005 10:34:23 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: md5sum problem on reading CD's
Message-ID: <20051012083423.GV12938@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20051012050347 DOT 36413 DOT qmail AT web51007 DOT mail DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051012050347.36413.qmail@web51007.mail.yahoo.com>
User-Agent: Mutt/1.4.2i

On Oct 11 22:03, Stilianos Kesisoglou wrote:
> Hi,
> 
> I've discovered an error in using the md5sum command
> to create a hash for a CD.
> 
> I was trying to burn a CD, from an ISO image of the
> Solaris CD1 that I downloaded from Sun's Download
> Center.
> 
> Before the burning process, I've calculated the md5
> hash for the ISO image using both Cygwin's md5sum
> command and ISOBuster's (that allows also to make the
> hash for 2048 and 2352 bytes/block).
> 
> For Cygwin's md5sum I used the command:
> 
>  %> md5sum sol-10-GA-x86-v1-iso.iso
> 
> The results for the hashes are below:
> 
> 3838f0e0560b4a1d9dc43a8cf754965a
> *sol-10-GA-x86-v1-iso.iso (with Cygwin's md5sum)
> 3838f0e0560b4a1d9dc43a8cf754965a *CD.tao (with
> ISOBuster - 2048 bytes/block)
> d1e3c9bbfc16cf0922d94afeeda2e756 *CD.bin (with
> ISOBuster - 2352 bytes/block)
> 
> So there is an agreement with for the hash (with the
> 2048 setting).
> 
> After burning the CD, I wanted to check the integrity
> of the burn so I've run again ISOBuster and Cygwin's
> md5sum.
> 
> For Cygwin I've used the command:
> 
>  %> md5sum /dev/scd0
> 
> and I got the following results:
> 
> eeba689f88d7a28e4ef54099db5c429c */dev/scd0 (with
> Cygwin's md5sum)
> 3838f0e0560b4a1d9dc43a8cf754965a *CD.tao (with
> ISOBuster - 2048 bytes/block)
> d1e3c9bbfc16cf0922d94afeeda2e756 *CD.bin (with
> ISOBuster - 2352 bytes/block)

I guess reading from /dev/scd0 reads all bits from the CD while ISOBuster
only reads the exact number of bytes burned on CD.

As I said, just a guess,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/