tips needed on iso files

Gregory Nowak greg at
Tue Jun 29 19:26:55 EDT 2004

Hash: SHA1

On Tue, Jun 29, 2004 at 06:18:29PM -0400, Chuck Hallenbeck wrote:
> 1. I have the four iso files for SW 10.0 (thanks, Greg) plus the
> associated md5 files. How do I verify the intactness of my
> downloads? The man page seems to suggest I should have a command
> called "md5" unless I am misreading it, but there ain't no such
> animal on my system. Related to that, I will then burn a set of
> CD's and will need to verify those burns as well.

Here is the easiest method.

1. Put the *.md5 files, and the *.iso files in the same directory.

2. Then issue the following command:

md5sum -c file.md5

here, file.md5 refers to the file containing the md5checksum. If the
file you're checking is ok, the md5sum program will tell you this
after a bit of a wait. If the file being verified doesn't match the
given checksum, you will be told that as well.

As for checking the burned cd images, I plan to modify the md5 file to
point to /dev/cdrom, instead of the file name of the iso image. In
theory, this should work, but I've never tried it.

> 2. There should be a way to "open" those iso files, copying or
> converting them to the corresponding files and directories,
> without first burning the CD's and then mounting and copying the
> contents back in again. How would you do that, going directly
> from an iso file to a directory structure on the HD?

There is a way to do that. Assuming you have the loop device compiled
into your kernel or as a module (this is not the same as the network
loopback device), you should be able to do:

mount -ro loop file.iso /cdrom

. This of course assumes that you want to mount file.iso onto the
/cdrom mount point. Hth.


- -- 
Free domains: or mail dns-manager at

Version: GnuPG v1.2.3 (GNU/Linux)


More information about the Speakup mailing list