From: Jason Pyeron <jpyeron@pdinc.us>
To: cygwin@cygwin.com
Subject: Re: md5sum problem on reading CD's
Date: Mon, 17 Oct 2005 14:20:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.62.0510171018480.3755@ns.pyerotechnics.com> (raw)
In-Reply-To: <20051012083423.GV12938@calimero.vinschen.de>
try
head -c SIZE /dev/scd0 | md5sum
if still broken
what is wc /dev/scd0
On Wed, 12 Oct 2005, Corinna Vinschen wrote:
> 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
>
>
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Partner & Sr. Manager 7 West 24th Street #100 -
- +1 (443) 921-0381 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you
have received it in error, purge the message from your system and
notify the sender immediately. Any other use of the email by you
is prohibited.
--
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/
prev parent reply other threads:[~2005-10-17 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 5:03 Stilianos Kesisoglou
2005-10-12 8:34 ` Corinna Vinschen
2005-10-17 14:20 ` Jason Pyeron [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.62.0510171018480.3755@ns.pyerotechnics.com \
--to=jpyeron@pdinc.us \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).