puppy-215CE-Final.iso strangeness

[rrolsbe]

Boots fine but.

Can I get someone who has successfully downloaded puppy-215CE-Final.iso to execute the md5sum command on the mounted cd. Md5sum output on the individual files might be a good thing to make available on the download servers, possibly as a text file on the iso, so a user can verify puppy cd/dvd boot media for errors. IE.. verify reader is reading correctly, cd/dvd not scratched etc.

sh-3.00# md5sum *
6a7ef1e62191f6f458ddaacdd881772d boot.cat
3c8c791f51c5e94868f006f10fa0782c boot.msg
74f698055f921229ab390a085e27a218 initrd.gz
c19705b8f39cf68a0f7d1d1db1e82456 isolinux.bin
2e2936dee94a837c6aaa5a55cb2deb16 isolinux.cfg
921d8982e498c310c00635c2d6df4d30 pup_215.sfs
952484a8a742d57595d7ae8b8118b7f1 vmlinuz
3f0b8ee47c50c9fc7045da023e46ae29 zdrv_215.sfs

Thanks Much
Regards
Ron

[GuestToo]

i have suggested putting an md5sum file in the iso, more than once

then you could easily check if each file in the iso or on the cd/dvd is a perfect copy or not

this does not check the entire disc, but it does check 99% of the disc, and it does verify all the files on the disk ... and the md5sum file is not very large

and it can help to check whether a cd/dvd disc burned correctly or not

[Béèm]

There is a difference on my machine for zdrv_215.sfs (april 06 17:58 )
What is the date/hour of yours?

sh-3.00# md5sum *
6a7ef1e62191f6f458ddaacdd881772d boot.cat
3c8c791f51c5e94868f006f10fa0782c boot.msg
74f698055f921229ab390a085e27a218 initrd.gz
c19705b8f39cf68a0f7d1d1db1e82456 isolinux.bin
2e2936dee94a837c6aaa5a55cb2deb16 isolinux.cfg
921d8982e498c310c00635c2d6df4d30 pup_215.sfs
952484a8a742d57595d7ae8b8118b7f1 vmlinuz
dd0815c9272204fafe92fe8bc8fc9555 zdrv_215.sfs
sh-3.00#

GuestToo made a good suggestion.

[Sit Heel Speak]

My zdrv_215.sfs agrees with Beem's. Both of them that I downloaded. One from the torrent and the other from richard.a's mirror.

[rrolsbe]

Must have gotten corrupted during the burning process or it is not reading correctly because the md5 checksum was correct for the iso. I should have kept the iso but I stored and burned it from RAM. Since puppy only has a handful of files, it could have a copy of the md5 checksum (maybe several copies for redundancy) included in the iso. IE... another plus for using puppy over most other distros.

Again
Thanks Very Much for the information!!!
Regards
Ron

PS -- maybe the scripts run during the startup process could check the md5 checksums on the core files, then warn the user. Wish I could download just the corrupted file, approx 1/10 the size of the ISO file, then I could fix my problem.

sh-3.00# ls -al
dr-xr-xr-x 1 root root 2048 Apr 6 15:58 .
drwxr-xr-x 12 root root 60 Apr 9 07:42 ..
-r-xr-xr-x 1 root root 2048 Apr 6 15:58 boot.cat
-r-xr-xr-x 1 root root 960 Apr 6 15:58 boot.msg
-r-xr-xr-x 1 root root 1316243 Apr 6 15:58 initrd.gz
-r-xr-xr-x 1 root root 10648 Apr 6 15:58 isolinux.bin
-r-xr-xr-x 1 root root 141 Apr 6 15:58 isolinux.cfg
-r-xr-xr-x 1 root root 116178944 Apr 6 15:58 pup_215.sfs
-r-xr-xr-x 1 root root 1751229 Apr 6 15:58 vmlinuz
-r-xr-xr-x 1 root root 17756160 Apr 6 15:58 zdrv_215.sfs

[Sit Heel Speak]

According to WhoDo, at

http://murga-linux.com/puppy/viewtopic.php?p=108734

zdrv_215.sfs is just zdrv_214.sfs, renamed.

zdrv_214.sfs is available at

http://distro.ibiblio.org/pub/linux/dis ... uppylinux/

However, its md5sum is

51d463b8507a7d0391225d00f64c3135

which is different. Anyone know why?

[WhoDo]

However, its md5sum is

51d463b8507a7d0391225d00f64c3135

which is different. Anyone know why?

Run md5sum AFTER renaming and it should match. I think the checksum includes the file name.

[GuestToo]

no, i don't think the name matters

basically, if 2 files have the same md5sum, it is almost certain that the 2 files are identical

if 2 files have different md5ums, it is almost certain that the 2 files are different, even if only by 1 byte

[richard.a]

i have suggested putting an md5sum file in the iso, more than once

then you could easily check if each file in the iso or on the cd/dvd is a perfect copy or not

this does not check the entire disc, but it does check 99% of the disc, and it does verify all the files on the disk ... and the md5sum file is not very large

and it can help to check whether a cd/dvd disc burned correctly or not

Good point. Though I burn wherever possible (and always with ISOs) in K3b in SuSE and I check the verify box before hitting the final (top right) burn button. If it believes the burn is a correct replication of the original ISO then one receives a message at the end of the verification that it believes it is "binary equal".

Having already compared the checksum it reads on loading the .iso file prior to burning, with the published md5, I figure this also gives a 99% probability of a good burn.

Richard