On Fri, 7 Oct 2005, Marcus Cooper wrote:

On 07/10/05, Aschwin Marsman wrote:

...

Hi,

I can't find the md5sum on the site of the CD's: 446af780a75e25e0ef3d86519704d61d SUSE-10.0-CD-OSS-i386-GM-CD1.iso f30f738a57f3bf3b185efa8b7013906a SUSE-10.0-CD-OSS-i386-GM-CD2.iso 49d451efb5844f4f99f7399a3d180094 SUSE-10.0-CD-OSS-i386-GM-CD3.iso 40e7517635abba36a3f506cbbcd823d1 SUSE-10.0-CD-OSS-i386-GM-CD4.iso d5bc32922ddb75adf7c19d770dfb0337 SUSE-10.0-CD-OSS-i386-GM-CD5.iso

Unless I'm missing your question completely (which is very possible as I'm half way through packing for going on holiday tomorrow) isn't the large hex number at the front of each of those lines the md5sum?

Yes, but those are mine after a download, I can't find the md5sum's to compare witha and I would like to know how to burn so you can perform a md5sum on the burned CD.

have fun

Marcus

Have a nice weekend, Aschwin Marsman -- aschwin@marsman.org http://www.marsman.org

Aschwin Marsman wrote:

On Fri, 7 Oct 2005, Marcus Cooper wrote:

...

On 07/10/05, Aschwin Marsman wrote:

...

Hi,

I can't find the md5sum on the site of the CD's: 446af780a75e25e0ef3d86519704d61d SUSE-10.0-CD-OSS-i386-GM-CD1.iso f30f738a57f3bf3b185efa8b7013906a SUSE-10.0-CD-OSS-i386-GM-CD2.iso 49d451efb5844f4f99f7399a3d180094 SUSE-10.0-CD-OSS-i386-GM-CD3.iso 40e7517635abba36a3f506cbbcd823d1 SUSE-10.0-CD-OSS-i386-GM-CD4.iso d5bc32922ddb75adf7c19d770dfb0337 SUSE-10.0-CD-OSS-i386-GM-CD5.iso

I found these MD5 hashes on the swiss mirror (ftp://mirror.switch.ch/mirror/opensuse)

446af780a75e25e0ef3d86519704d61d SUSE-10.0-CD-OSS-i386-GM-CD1.iso f30f738a57f3bf3b185efa8b7013906a SUSE-10.0-CD-OSS-i386-GM-CD2.iso 49d451efb5844f4f99f7399a3d180094 SUSE-10.0-CD-OSS-i386-GM-CD3.iso 40e7517635abba36a3f506cbbcd823d1 SUSE-10.0-CD-OSS-i386-GM-CD4.iso d5bc32922ddb75adf7c19d770dfb0337 SUSE-10.0-CD-OSS-i386-GM-CD5.iso 8ac286bcb1f3ffa4ae766fbbdf44ee85 SUSE-10.0-CD-OSS-ppc-GM-CD1.iso 761dede42744ff53f63dac3f9e7f9661 SUSE-10.0-CD-OSS-ppc-GM-CD2.iso a0952db6e4e14018f0d840d25afcd6f4 SUSE-10.0-CD-OSS-ppc-GM-CD3.iso 3092c7e7431d0e27d1473438bba0d369 SUSE-10.0-CD-OSS-ppc-GM-CD4.iso 759833cab88246c71749f85c7a6d8cef SUSE-10.0-CD-OSS-ppc-GM-CD5.iso 40a3ed3ca88b2256bfced3b0b91b4518 SUSE-10.0-CD-OSS-x86_64-GM-CD1.iso b7455b461387e35937c17488300e6a63 SUSE-10.0-CD-OSS-x86_64-GM-CD2.iso ab1ded581c026af47bdbf9d5a75f0240 SUSE-10.0-CD-OSS-x86_64-GM-CD3.iso 660538b9795968652d6392457c9606f1 SUSE-10.0-CD-OSS-x86_64-GM-CD4.iso d79e61abb9bbf25bcb7b244d3ca92d9a SUSE-10.0-CD-OSS-x86_64-GM-CD5.iso *** So it seems to me your downloads went fine. Greetings, Dominique

On Sat, 8 Oct 2005, Thierry de Coulon wrote:-

On Friday, 7 October 2005 22:07, Aschwin Marsman wrote:

...

Yes, but those are mine after a download, I can't find the md5sum's to compare witha and I would like to know how to burn so you can perform a md5sum on the burned CD.

I think they don't put the md2sums because the installer contains a feature to test the integrity of your CD's: before installing you get this option.

If you download via FTP or HTTP, the mirrors do have an MD5SUMS file in the same directory as the images so you can check the download was correct. Unfortunately, when you download using the torrents, the MD5SUMS for the images aren't included and I feel this isn't a good thing. It would be better if all the torrents supplied a separate MD5SUMS file for the supplied images, e.g. MD5SUMS.i386, MD5SUMS.ppc or MD5SUMS.x86_64. This should also apply to the torrents for the delta.isos, where the MD5SUMS should also include the final image MD5SUMS. Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD 1800 1Gb WinXP/SuSE 9.3 | AMD 2400 160Mb SuSE 8.1 | AMD 2400 256Mb SuSE 9.0 AMD 1300 512Mb SuSE 9.0 | Falcon 14Mb TOS 4.02 | STE 4Mb TOS 1.62 RPC600 129Mb RISCOS 3.6 | A3010 4Mb RISCOS 3.11 | A4000 4Mb RISCOS 3.11

Johannes Kastl writes:

On 10/8/2005 5:32 PM David Bolt wrote:

...

Unfortunately, when you download using the torrents, the MD5SUMS for the images aren't included and I feel this isn't a good thing. It would be better if all the torrents supplied a separate MD5SUMS file for the supplied images, e.g. MD5SUMS.i386, MD5SUMS.ppc or MD5SUMS.x86_64.

This is going to change, there was a mail on the list today or yesterday.

The mail said: We try to change it - not a direct promise, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

Johannes Kastl writes:

On 10/8/2005 6:50 PM Andreas Jaeger wrote:

...

The mail said: We try to change it - not a direct promise,

Boooooh!

To be honest: Do you think you would fail on that?

It's not me doing it ;)

I trust in your skills ;-)

I trust in them as well, it just needs a little bit of time and doing it the right way;-) Cheers, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

On Sat, 8 Oct 2005, Guðlaugur Jóhannesson wrote:

David Bolt wrote:

...

Unfortunately, when you download using the torrents, the MD5SUMS for the images aren't included and I feel this isn't a good thing. It would be better if all the torrents supplied a separate MD5SUMS file for the supplied images, e.g. MD5SUMS.i386, MD5SUMS.ppc or MD5SUMS.x86_64.

It is not needed as BitTorrent already does this. Here is an answer from their FAQ http://www.bittorrent.com/FAQ.html#corruptdl

So we do not need md5sum check after downloading the torrents.

I don't agree, I would like to check the images after burning without using the installation procedure. Yesterday a brand new cdrw failed while burning, and I needed a reboot in order to use the device again ;-(. This indicated that I could throw away the cdrw, but if only one bit would fail I wouldn't notice. Still my original question stands: how to burn an iso so you can do a md5sum on the resulting cd? I didn't find the pad option is cdrecord when I tried during SUSE 9.3.

Cheers Gulli

Best regards, Aschwin Marsman -- aschwin@marsman.org http://www.marsman.org

On Sun, 9 Oct 2005, Randall R Schulz wrote: Randall, Thanx for your reply.

In SuSE Linux 9.3 or 10.0, YaST includes a distribution media verification function. It will work for CDs and DVDs released by SuSE (and openSUSE? -- probably). Insert the disc you burned, start YaST, select the "Software" section and activate "Media Check" and click "Start".

I know, and that always fails on the CD's I burned, but they work correctly. I think it has something to do with padding, but I don't know how to burn them correctly.

Randall Schulz

Best regards, Aschwin Marsman -- aschwin@marsman.org http://www.marsman.org

On Mon, 10 Oct 2005, Andreas Jaeger wrote: Thanks for your reply.

...

I know, and that always fails on the CD's I burned, but they work correctly. I think it has something to do with padding, but I don't know how to burn them correctly.

My burn commands are:

burning CDs: cdrecord fs=2M -dao -eject -v -data -pad speed=52 -isosize dev=/dev/hdd driveropts=burnfree "$@"

burning DVDs: growisofs -dvd-compat -Z /dev/hdd="$@"

This is what I was looking for, thanks.

Somebody might add these to the wiki download page - with these commands you get the padding and md5sum works for me unless I have a real problem,

Andreas

Best regards, Aschwin Marsman -- aschwin@marsman.org http://www.marsman.org