[opensuse] Checksums, openSuSE downloads, md5sum
Hi list, - and a HAPPY NEW YEAR TO ALL! - I'm puzzled by md5sums. I've downloaded openSuSE11 (both 32 and 64 bit versions) and openSuSE11.1 (32/64 too). - I get the same odd errors with 11 as with 11.1. This is my situation: I try to verify the md5sum of openSuSE11(i386/32), it should be ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso but using "md5sum openSUSE-11.0-DVD-i386.iso", I get: a38623810009842eeb1542a2052cfc2d openSUSE-11.0-DVD-i386.iso This, of course, is wrong. If I do a "md5sum -c openSUSE-11.0-DVD-i386.iso", I get 500+ lines saying the this or that -rpm file could not be read, general i/o error or so" Now if I burn an ISO DVD, it verifies correctly when doing the "check media" before installation (!). Installation starts fine, but in some cases breaks later on, but not always... I use K3B for burning, it reports a sound md5sum. I downloaded the isos from mirrors and directly from SuSE too. I downloaded from two different locations, albeit to the same PC (my laptop). I stored the received files (during download) onto the harddisk and also onto a USB stick. Same story. As you can tell, I've done quite a few downloads...All the downloaded files yield the same md5sum (using md5sum without the -c flag), never mind what media I store onto. And regardless of wherefrom and my method of downloading. As of now, I'm not really able to install openSuSE11(1) to anything, as I can't seem to get this right. Questions: a) The md5sums listed on the openSuSE web are (of course) correct b) what's the correct and proper way of verifying the md5sums? c) I used wget, firefox directly and a FF-extension called DownThenAll for downloading. What would be your recommendation? And as always, thank you! -- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dne četrtek 01 januar 2009 ob 11:21:04 je Verner Kjærsgaard napisal(a):
Hi list,
- and a HAPPY NEW YEAR TO ALL!
- I'm puzzled by md5sums. I've downloaded openSuSE11 (both 32 and 64 bit versions) and openSuSE11.1 (32/64 too).
- I get the same odd errors with 11 as with 11.1. This is my situation:
I try to verify the md5sum of openSuSE11(i386/32), it should be
ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso
but using "md5sum openSUSE-11.0-DVD-i386.iso", I get:
a38623810009842eeb1542a2052cfc2d openSUSE-11.0-DVD-i386.iso
This, of course, is wrong. If I do a
"md5sum -c openSUSE-11.0-DVD-i386.iso", I get 500+ lines saying the this or that -rpm file could not be read, general i/o error or so"
Now if I burn an ISO DVD, it verifies correctly when doing the "check media" before installation (!). Installation starts fine, but in some cases breaks later on, but not always... I use K3B for burning, it reports a sound md5sum.
I downloaded the isos from mirrors and directly from SuSE too. I downloaded from two different locations, albeit to the same PC (my laptop). I stored the received files (during download) onto the harddisk and also onto a USB stick.
Same story. As you can tell, I've done quite a few downloads...All the downloaded files yield the same md5sum (using md5sum without the -c flag), never mind what media I store onto. And regardless of wherefrom and my method of downloading.
As of now, I'm not really able to install openSuSE11(1) to anything, as I can't seem to get this right.
Questions:
a) The md5sums listed on the openSuSE web are (of course) correct
b) what's the correct and proper way of verifying the md5sums?
c) I used wget, firefox directly and a FF-extension called DownThenAll for downloading. What would be your recommendation?
And as always, thank you!
-- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard
a) of course b) just let k3b do it automatically (when it reads-in an ISO) and visually compare it with a) c) all your methods are correct. If you want additional error-checking, you can use ktorrent with the torrent links; then, when ktorrent downloads the ISO, you right-click on the ISO and select "Check data" from the pop-up menu. d) I'm suspecting your CD/DVD writer may be oldish or a bit incompatible, or maybe the media are not overly compatible with your particular optical drive. In addition, check all k3b settings and verify they're all set to defaults. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.00.0901011237550.6052@nimrodel.valinor> On Thursday, 2009-01-01 at 11:21 +0100, Verner Kjærsgaard wrote:
Hi list,
- and a HAPPY NEW YEAR TO ALL!
Same to you :-)
- I'm puzzled by md5sums. I've downloaded openSuSE11 (both 32 and 64 bit versions) and openSuSE11.1 (32/64 too).
- I get the same odd errors with 11 as with 11.1. This is my situation:
I try to verify the md5sum of openSuSE11(i386/32), it should be
ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso
ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso Correct, yes.
but using "md5sum openSUSE-11.0-DVD-i386.iso", I get:
a38623810009842eeb1542a2052cfc2d openSUSE-11.0-DVD-i386.iso
This, of course, is wrong. If I do a
yep, wrong.
"md5sum -c openSUSE-11.0-DVD-i386.iso", I get 500+ lines saying the this or that -rpm file could not be read, general i/o error or so"
Actually, it should be: md5sum -c MD5SUMS where "MD5SUMS" is the file containing the text line above, ie, the checksums and filenames.
Now if I burn an ISO DVD, it verifies correctly when doing the "check media" before installation (!).
What!? I would report that as a bug.
Installation starts fine, but in some cases breaks later on, but not always... I use K3B for burning, it reports a sound md5sum.
Well, it reports that it burned correctly the image you gave it, which we know is bad.
I downloaded the isos from mirrors and directly from SuSE too. I downloaded from two different locations, albeit to the same PC (my laptop). I stored the received files (during download) onto the harddisk and also onto a USB stick.
And all of them have the same (incorrect) checksum?
Same story. As you can tell, I've done quite a few downloads...All the downloaded files yield the same md5sum (using md5sum without the -c flag), never mind what media I store onto. And regardless of wherefrom and my method of downloading.
The same incorrect checksum? All of them? Wow. By the way, check the image before burning it. If it is incorrect, don't bother burning.
As of now, I'm not really able to install openSuSE11(1) to anything, as I can't seem to get this right.
Questions:
a) The md5sums listed on the openSuSE web are (of course) correct
b) what's the correct and proper way of verifying the md5sums?
md5sum -c md5sumfilename
c) I used wget, firefox directly and a FF-extension called DownThenAll for downloading. What would be your recommendation?
aria2c (metalink link), from here: http://download.opensuse.org/distribution/11.0/iso/dvd/ if you want the 11.0 version, or http://download.opensuse.org/distribution/11.1/iso/ if you want the new, 11.1 version. Use the comand line program "aria2c", feeding it the "metalink" link address; for example: aria2c --max-download-limit=85K --max-upload-limit=12K http://download.opensuse.org/distribution/11.1/iso/openSUSE-11.1-DVD-i586.is... you will have to download aria2c first, though. Info on "metalink": <http://en.opensuse.org/Download_Help#Downloading_via_Metalinks> The reason is that this method should provide a corrected iso file. More info here: <http://lizards.opensuse.org/2008/12/16/best-way-to-download-opensuse/> Another method, as you already have the image, with errors, is to repair it. Here you have instructions: <http://en.opensuse.org/Download_Help#Repairing_a_Download> - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklcq9gACgkQtTMYHG2NR9VPvgCeMW/LsHS20OKv8+D9hiWQqkFz WNgAoIi2tIa1WsPYhYn0lWMBKItbw0uA =i2xL -----END PGP SIGNATURE-----
Carlos E. R. skrev:
Content-ID: <alpine.LSU.2.00.0901011237550.6052@nimrodel.valinor>
On Thursday, 2009-01-01 at 11:21 +0100, Verner Kjærsgaard wrote:
Hi list,
- and a HAPPY NEW YEAR TO ALL!
Same to you :-)
- I'm puzzled by md5sums. I've downloaded openSuSE11 (both 32 and 64 bit versions) and openSuSE11.1 (32/64 too).
- I get the same odd errors with 11 as with 11.1. This is my situation:
I try to verify the md5sum of openSuSE11(i386/32), it should be
ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso
ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso
Correct, yes.
but using "md5sum openSUSE-11.0-DVD-i386.iso", I get:
a38623810009842eeb1542a2052cfc2d openSUSE-11.0-DVD-i386.iso
This, of course, is wrong. If I do a
yep, wrong.
"md5sum -c openSUSE-11.0-DVD-i386.iso", I get 500+ lines saying the this or that -rpm file could not be read, general i/o error or so"
Actually, it should be:
md5sum -c MD5SUMS
where "MD5SUMS" is the file containing the text line above, ie, the checksums and filenames.
Now if I burn an ISO DVD, it verifies correctly when doing the "check media" before installation (!).
What!?
I would report that as a bug.
Installation starts fine, but in some cases breaks later on, but not always... I use K3B for burning, it reports a sound md5sum.
Well, it reports that it burned correctly the image you gave it, which we know is bad.
I downloaded the isos from mirrors and directly from SuSE too. I downloaded from two different locations, albeit to the same PC (my laptop). I stored the received files (during download) onto the harddisk and also onto a USB stick.
And all of them have the same (incorrect) checksum?
Same story. As you can tell, I've done quite a few downloads...All the downloaded files yield the same md5sum (using md5sum without the -c flag), never mind what media I store onto. And regardless of wherefrom and my method of downloading.
The same incorrect checksum? All of them? Wow.
By the way, check the image before burning it. If it is incorrect, don't bother burning.
As of now, I'm not really able to install openSuSE11(1) to anything, as I can't seem to get this right.
Questions:
a) The md5sums listed on the openSuSE web are (of course) correct
b) what's the correct and proper way of verifying the md5sums?
md5sum -c md5sumfilename
c) I used wget, firefox directly and a FF-extension called DownThenAll for downloading. What would be your recommendation?
aria2c (metalink link), from here:
http://download.opensuse.org/distribution/11.0/iso/dvd/
if you want the 11.0 version, or
http://download.opensuse.org/distribution/11.1/iso/
if you want the new, 11.1 version. Use the comand line program "aria2c", feeding it the "metalink" link address; for example:
aria2c --max-download-limit=85K --max-upload-limit=12K http://download.opensuse.org/distribution/11.1/iso/openSUSE-11.1-DVD-i586.is...
you will have to download aria2c first, though.
Info on "metalink":
<http://en.opensuse.org/Download_Help#Downloading_via_Metalinks>
The reason is that this method should provide a corrected iso file. More info here:
<http://lizards.opensuse.org/2008/12/16/best-way-to-download-opensuse/>
Another method, as you already have the image, with errors, is to repair it. Here you have instructions:
<http://en.opensuse.org/Download_Help#Repairing_a_Download>
-- Cheers, Carlos E. R.
Thank You! - so much knowledge and info, so little time :-) - I'll get on to it right away, first I dig into aria2c. Oil keep you posted, said the sheik! Best regards, Verner -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I find failing md5 tests often indicate hardware problems, so I would also investigate hardware issues on you PC. First I'd run memtest from the boot dvd first as an overnight test. Greg On Thu, Jan 1, 2009 at 10:28 AM, Verner Kjærsgaard <vk@os-academy.dk> wrote:
Carlos E. R. skrev:
Content-ID: <alpine.LSU.2.00.0901011237550.6052@nimrodel.valinor>
On Thursday, 2009-01-01 at 11:21 +0100, Verner Kjærsgaard wrote:
Hi list,
- and a HAPPY NEW YEAR TO ALL!
Same to you :-)
- I'm puzzled by md5sums. I've downloaded openSuSE11 (both 32 and 64 bit versions) and openSuSE11.1 (32/64 too).
- I get the same odd errors with 11 as with 11.1. This is my situation:
I try to verify the md5sum of openSuSE11(i386/32), it should be
ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso
ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso
Correct, yes.
but using "md5sum openSUSE-11.0-DVD-i386.iso", I get:
a38623810009842eeb1542a2052cfc2d openSUSE-11.0-DVD-i386.iso
This, of course, is wrong. If I do a
yep, wrong.
"md5sum -c openSUSE-11.0-DVD-i386.iso", I get 500+ lines saying the this or that -rpm file could not be read, general i/o error or so"
Actually, it should be:
md5sum -c MD5SUMS
where "MD5SUMS" is the file containing the text line above, ie, the checksums and filenames.
Now if I burn an ISO DVD, it verifies correctly when doing the "check media" before installation (!).
What!?
I would report that as a bug.
Installation starts fine, but in some cases breaks later on, but not always... I use K3B for burning, it reports a sound md5sum.
Well, it reports that it burned correctly the image you gave it, which we know is bad.
I downloaded the isos from mirrors and directly from SuSE too. I downloaded from two different locations, albeit to the same PC (my laptop). I stored the received files (during download) onto the harddisk and also onto a USB stick.
And all of them have the same (incorrect) checksum?
Same story. As you can tell, I've done quite a few downloads...All the downloaded files yield the same md5sum (using md5sum without the -c flag), never mind what media I store onto. And regardless of wherefrom and my method of downloading.
The same incorrect checksum? All of them? Wow.
By the way, check the image before burning it. If it is incorrect, don't bother burning.
As of now, I'm not really able to install openSuSE11(1) to anything, as I can't seem to get this right.
Questions:
a) The md5sums listed on the openSuSE web are (of course) correct
b) what's the correct and proper way of verifying the md5sums?
md5sum -c md5sumfilename
c) I used wget, firefox directly and a FF-extension called DownThenAll for downloading. What would be your recommendation?
aria2c (metalink link), from here:
http://download.opensuse.org/distribution/11.0/iso/dvd/
if you want the 11.0 version, or
http://download.opensuse.org/distribution/11.1/iso/
if you want the new, 11.1 version. Use the comand line program "aria2c", feeding it the "metalink" link address; for example:
aria2c --max-download-limit=85K --max-upload-limit=12K http://download.opensuse.org/distribution/11.1/iso/openSUSE-11.1-DVD-i586.is...
you will have to download aria2c first, though.
Info on "metalink":
<http://en.opensuse.org/Download_Help#Downloading_via_Metalinks>
The reason is that this method should provide a corrected iso file. More info here:
<http://lizards.opensuse.org/2008/12/16/best-way-to-download-opensuse/>
Another method, as you already have the image, with errors, is to repair it. Here you have instructions:
<http://en.opensuse.org/Download_Help#Repairing_a_Download>
-- Cheers, Carlos E. R.
Thank You!
- so much knowledge and info, so little time :-) - I'll get on to it right away, first I dig into aria2c. Oil keep you posted, said the sheik!
Best regards, Verner
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Greg Freemyer skrev:
I find failing md5 tests often indicate hardware problems, so I would also investigate hardware issues on you PC.
First I'd run memtest from the boot dvd first as an overnight test.
Greg
On Thu, Jan 1, 2009 at 10:28 AM, Verner Kjærsgaard <vk@os-academy.dk> wrote:
Carlos E. R. skrev:
Content-ID: <alpine.LSU.2.00.0901011237550.6052@nimrodel.valinor>
On Thursday, 2009-01-01 at 11:21 +0100, Verner Kjærsgaard wrote:
Hi list,
- and a HAPPY NEW YEAR TO ALL! Same to you :-)
- I'm puzzled by md5sums. I've downloaded openSuSE11 (both 32 and 64 bit versions) and openSuSE11.1 (32/64 too). - I get the same odd errors with 11 as with 11.1. This is my situation: I try to verify the md5sum of openSuSE11(i386/32), it should be ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso
Correct, yes.
but using "md5sum openSUSE-11.0-DVD-i386.iso", I get: a38623810009842eeb1542a2052cfc2d openSUSE-11.0-DVD-i386.iso This, of course, is wrong. If I do a yep, wrong.
"md5sum -c openSUSE-11.0-DVD-i386.iso", I get 500+ lines saying the this or that -rpm file could not be read, general i/o error or so" Actually, it should be:
md5sum -c MD5SUMS
where "MD5SUMS" is the file containing the text line above, ie, the checksums and filenames.
Now if I burn an ISO DVD, it verifies correctly when doing the "check media" before installation (!). What!?
I would report that as a bug.
Installation starts fine, but in some cases breaks later on, but not always... I use K3B for burning, it reports a sound md5sum. Well, it reports that it burned correctly the image you gave it, which we know is bad.
I downloaded the isos from mirrors and directly from SuSE too. I downloaded from two different locations, albeit to the same PC (my laptop). I stored the received files (during download) onto the harddisk and also onto a USB stick. And all of them have the same (incorrect) checksum?
Same story. As you can tell, I've done quite a few downloads...All the downloaded files yield the same md5sum (using md5sum without the -c flag), never mind what media I store onto. And regardless of wherefrom and my method of downloading. The same incorrect checksum? All of them? Wow.
By the way, check the image before burning it. If it is incorrect, don't bother burning.
As of now, I'm not really able to install openSuSE11(1) to anything, as I can't seem to get this right. Questions: a) The md5sums listed on the openSuSE web are (of course) correct b) what's the correct and proper way of verifying the md5sums? md5sum -c md5sumfilename
c) I used wget, firefox directly and a FF-extension called DownThenAll for downloading. What would be your recommendation? aria2c (metalink link), from here:
http://download.opensuse.org/distribution/11.0/iso/dvd/
if you want the 11.0 version, or
http://download.opensuse.org/distribution/11.1/iso/
if you want the new, 11.1 version. Use the comand line program "aria2c", feeding it the "metalink" link address; for example:
aria2c --max-download-limit=85K --max-upload-limit=12K http://download.opensuse.org/distribution/11.1/iso/openSUSE-11.1-DVD-i586.is...
you will have to download aria2c first, though.
Info on "metalink":
<http://en.opensuse.org/Download_Help#Downloading_via_Metalinks>
The reason is that this method should provide a corrected iso file. More info here:
<http://lizards.opensuse.org/2008/12/16/best-way-to-download-opensuse/>
Another method, as you already have the image, with errors, is to repair it. Here you have instructions:
<http://en.opensuse.org/Download_Help#Repairing_a_Download>
-- Cheers, Carlos E. R. Thank You!
- so much knowledge and info, so little time :-) - I'll get on to it right away, first I dig into aria2c. Oil keep you posted, said the sheik!
Best regards, Verner
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thanks to all for their excellent help! I used aria2c to download the openSuSE11.0/32bit DVD, it went quick and it verifies fine. Now I fire up K3B...and did you hear the drums? ta - da ! It worked! On the first day of the new year, I (again) learnt something! Thanks :-) -- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard Open Source Academy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-01-01 at 19:58 +0100, Verner Kjærsgaard wrote:
Thanks to all for their excellent help! I used aria2c to download the openSuSE11.0/32bit DVD, it went quick and it verifies fine. Now I fire up K3B...and did you hear the drums?
ta - da !
It worked! On the first day of the new year, I (again) learnt something! Thanks :-)
Welcome! I guess we have a new aria2c convert ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkldHsAACgkQtTMYHG2NR9VtCACdETJ2ygt7knp5r0LVInG2W7ip ig8AnioFL3gkTu6wSwf0L+Y3Q2CPsuVy =CWgb -----END PGP SIGNATURE-----
Carlos E. R. skrev:
On Thursday, 2009-01-01 at 19:58 +0100, Verner Kjærsgaard wrote:
Thanks to all for their excellent help! I used aria2c to download the openSuSE11.0/32bit DVD, it went quick and it verifies fine. Now I fire up K3B...and did you hear the drums?
ta - da !
It worked! On the first day of the new year, I (again) learnt something! Thanks :-)
Welcome! I guess we have a new aria2c convert ;-)
-- Cheers, Carlos E. R.
- a convert, an advocate and an evangelist :-) - it works like a breeze! -- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Verner Kjærsgaard wrote:
Carlos E. R. skrev:
On Thursday, 2009-01-01 at 19:58 +0100, Verner Kjærsgaard wrote:
Thanks to all for their excellent help! I used aria2c to download the openSuSE11.0/32bit DVD, it went quick and it verifies fine. Now I fire up K3B...and did you hear the drums?
ta - da !
It worked! On the first day of the new year, I (again) learnt something! Thanks :-)
Welcome! I guess we have a new aria2c convert ;-)
-- Cheers, Carlos E. R.
- a convert, an advocate and an evangelist :-) - it works like a breeze!
Just don't get too enthused :-) . Following comment is not directed at aria2c nor at k3's ability to burn a DVD and then verify it as being "successful". Burning DVDs under k3 works fine. Using k3 you will find - I do, and have been doing so for some months - that if you burn a *CD* and have the verify function set then every time the verification process will show that there is an error in the copy compared to the original -- however, there is NO error, but k3 always reports that there is an error. (BTW, just on this point of the verification process reporting an error in the copy: what a total waste of time that k3 has to ALWAYS check though the *whole* CD or DVD (upt o 8GB big) to report an error even though the error may have occurred at some point at the beginning of the CD or DVD. Why not report and stop further checking when the error is first detected?) Ciao. -- Be nice to people on your way up - you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2009-01-02 at 16:05 +1100, Basil Chupin wrote:
Following comment is not directed at aria2c nor at k3's ability to burn a DVD and then verify it as being "successful". Burning DVDs under k3 works fine.
Using k3 you will find - I do, and have been doing so for some months - that if you burn a *CD* and have the verify function set then every time the verification process will show that there is an error in the copy compared to the original -- however, there is NO error, but k3 always reports that there is an error.
Yes, I think I have seen this behaviour.
(BTW, just on this point of the verification process reporting an error in the copy: what a total waste of time that k3 has to ALWAYS check though the *whole* CD or DVD (upt o 8GB big) to report an error even though the error may have occurred at some point at the beginning of the CD or DVD. Why not report and stop further checking when the error is first detected?)
Because they don't do a byte by byte compare, but a calculation of a checksum. The checksum algorithm requires read the entire data stream. The byte compare needs reading two streams simultaneously, an average of half way: thus the same total data flow, at a slower pace, probably. They could have both algorithms and let the user choose. I usually burn by command line, my own script, and byte compare the result. I can use k3b to generate the iso image. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkld85IACgkQtTMYHG2NR9VNzACaA1uUQrqyMvQ7sZlXsSxNxauL /wIAoIL4t15qTk94e1vCW7Yfo2+QhpYX =A9Or -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Friday, 2009-01-02 at 16:05 +1100, Basil Chupin wrote:
Following comment is not directed at aria2c nor at k3's ability to burn a DVD and then verify it as being "successful". Burning DVDs under k3 works fine.
Using k3 you will find - I do, and have been doing so for some months - that if you burn a *CD* and have the verify function set then every time the verification process will show that there is an error in the copy compared to the original -- however, there is NO error, but k3 always reports that there is an error.
Yes, I think I have seen this behaviour.
Yes, but have you submitted a bug report about it, have you, have you, eh? :-) :-) .
(BTW, just on this point of the verification process reporting an error in the copy: what a total waste of time that k3 has to ALWAYS check though the *whole* CD or DVD (upt o 8GB big) to report an error even though the error may have occurred at some point at the beginning of the CD or DVD. Why not report and stop further checking when the error is first detected?)
Because they don't do a byte by byte compare, but a calculation of a checksum. The checksum algorithm requires read the entire data stream. The byte compare needs reading two streams simultaneously, an average of half way: thus the same total data flow, at a slower pace, probably.
OK, good point.
They could have both algorithms and let the user choose.
As you know, the available option at the moment is to either to Verify or not to Verify -- I think this is fine. However, what the Verify could do ( as an answer to the byte-by-byte check) is to do a sector to sector verification, and repeat this verification should an error be found, and then stop when an error is confirmed.
I usually burn by command line, my own script, and byte compare the result. I can use k3b to generate the iso image.
But for us mere mortals such niceties are not available................ Ciao. -- "With the portion of mankind that is above average one may speak of higher things; with those below it, one may not." Confucius -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. schreef:
Welcome! I guess we have a new aria2c convert ;-)
Make that two. :-) -- Jos van Kan registered Linux user #152704 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Jan 02, 2009 at 12:36:52AM +0100, Jos van Kan wrote:
Carlos E. R. schreef:
Welcome! I guess we have a new aria2c convert ;-)
Make that two. :-) -- Jos van Kan registered Linux user #152704
It is great to see these satisfying results. Carlos, thank you very much for spreading the word. I surely hope that this will be used much more in the future! Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Basil Chupin -
Carlos E. R. -
Greg Freemyer -
Jos van Kan -
JosipBroz -
Peter Poeml -
Verner Kjærsgaard