| 1 |
2009/11/18 José Romildo Malaquias <j.romildo@×××××.com>: |
| 2 |
> On Tue, Nov 17, 2009 at 04:54:20PM +0000, Grant Edwards wrote: |
| 3 |
>> On 2009-11-17, Marcus Wanner <marcusw@×××.net> wrote: |
| 4 |
>> |
| 5 |
>> > My guess is that he has a slow internet connection, he |
| 6 |
>> > downloaded a large iso, burned it, deleted it, and now wants |
| 7 |
>> > to get the iso back without downloading it again, but he has |
| 8 |
>> > access to the checksum/filesize of the original iso from the |
| 9 |
>> > place he downloaded it, and when he makes an iso, the |
| 10 |
>> > checksum/filesize does not match. |
| 11 |
>> |
| 12 |
>> In my experience that happens because one or the other of the |
| 13 |
>> images has "extra" garbage blocks past the end of the actual |
| 14 |
>> ISO filesystem image. If you look at the ISO filesystem header |
| 15 |
>> and find the actual size of the image, it's probably smaller |
| 16 |
>> than the "image file". If you only compare the bytes within |
| 17 |
>> the ISO image itself, I bet the two will match. |
| 18 |
> |
| 19 |
> In fact the size of the iso images obtained with dd and with cdread are |
| 20 |
> a little bit larger than the original one. The iso image obtained by |
| 21 |
> mkisofs on the mounted disc (with the udf filesystem type) are of the |
| 22 |
> right size, but still not identical to the original. |
| 23 |
|
| 24 |
This webpage has some info about comaring ISO images to burnt discs |
| 25 |
and a possible solution: |
| 26 |
http://twiki.org/cgi-bin/view/Wikilearn/CdromMd5sumsAfterBurning |
Archives