The January issue of Linux Format magazine has a 3 disk set of the latest Fedora on it's dvd issue, for those that are interested in that route.
===============================================================
Curtis Sloan wrote:


On Wed, 2004-01-21 at 13:29, Jason Louie wrote:

Thanks Curtis, that explains things.  Now the question remains.  How
to verify the CD after it's been burnt?  You stated before that there
are checksums that certain distros provide.  But I haven't been able
to find such a list, (ie: fedora).


You're right, I have not been able to find a comprehensive list of
MD5sums for Fedora either.  I'm not current on Fedora's
existence/development, but possibly there isn't a comprehensive one
(yet) and one would have to compile a list from Red Hat + individual
Fedora contributions.  I could be out to lunch.  I hope so for your
sake.  :-)

I won't start a distro war, but I will say "Thank you, Patrick
(Volkerding)!"  ;-)

Curtis


 Just want to make sure that the CD is good before offering it to
others.


Curtis Sloan wrote:


On Wed, 2004-01-21 at 11:43, Jason Louie wrote:


But is this producing the same MD5 checksum directly from the CD as
the ISO?

I'm not sure if I understand what you are asking, so let me rephrase the question and you can correct me if I'm misunderstanding:

"Is the MD5 checksum of the CD (i.e. /dev/cdrom) the same as the MD5
checksum of the .iso file (before it was burned)?"

If this is the question you are asking, then the answer is no.  They
will always be different.

The answer lies is in the way the MD5 algorithm works.  It produces a
unique 128-bit checksum for any given arrangement of bytes.

In this case, the arrangement of the bytes in an ISO file is distinctly
different than that of the exact same bytes laid out in a filesystem
(i.e. after burning).  The MD5 algorithm doesn't care that they are the
same bytes, since (from the algorithm's perspective) the single ISO file
is fundamentally different than the collection of files taken as a
whole.  One MD5 will be a "fingerprint" of an ISO file, the other of an
entire filesystem.  The difference can seem semantic, but viewed from an
algorithm's point of view, it can make sense.

This may account for apparent discrepancies in MD5s (if I understood
your question correctly).

HTH,
Curtis



I've seem lots of examples on the web on the process of verifying CDs
burnt from ISOs but I can't seem to reproduce the results.  I only
have access to a burner on a Win system and I'm wondering if that is
the reason why the MD5s are different.

Pete wrote:


Linux commandline burning works for me...

http://www.yolinux.com/TUTORIALS/LinuxTutorialCDBurn.html

There are a few examples of commands to copy CDs

Peter

Jason Louie wrote:


Has anyone been able to verify the *burned* copy of the ISO?  Also
what programs are you guys using for the burning?  I'm using Nero
on a Win system.  I have lots of distros that I would like to
share but I don't feel good about having them available when I'm
not sure if they're good.  I haven't been able to get matching
results with doing an MD5 check on the CD so I was wondering if
anyone has been getting better results.



_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca



--

  ---------------------------------------------------------------------
                    Dave Bourassa at
        http://members.shaw.ca/djb.enterprises/
                mailto:[EMAIL PROTECTED]
  ---------------------------------------------------------------------
     "There are 10 kinds of people in the world. Those who
          understand binary and those who don't."
  ---------------------------------------------------------------------



_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca

Reply via email to