Installing Suse 10.1
Most of the time I like to download via bittorrent, but I didn't this time.
I always check the MD5SUMS of ISOs before burning CDs, but I didn't this time.
If the installer has a function to validate the CDs I always use it, except for this time.
So, it should come as no surprise that CDs two and five were cut from corrupted ISOs, causing the install to bomb.
So, now I have to download the ISOs for CDs two and five again. But wait, what's that in the sky? Is it a bird? Is it a plane? Is it a pheasant? Is it perhaps a large slice of cheesecake, or a gorilla in a man-suit?
But, anyway, back to the story...
When we last met our intreped installaholic had just discovered that two of the five disc images he downloaded were corrupt. Possibly due to it being an election year, or something. Watch now as he learns an important lesson - all that glitters is not glitter, although most of it probably is.
... So, faced with the daunting task... well, not exactly daunting, because I am so damn good I am practically a superhero, or a lesbian pirate... So, faced with the oh so trivial task of downloading two full discs all over again, which would put an end to my plan of finishing the Suse install tonight, I laugh a mocking laugh, a manly mocking laugh. "Ha Ha," I laugh, mockingly, for I have a plan.
I navigate to the opensuse download page, and click the link to the torrent file. Bittornado pops up and asks where I would like to save the files. Now here is the tricky bit. The clever bit. I tell it to put them in ~/downloads, which just happens to be the exact location of the five Suse Linux 10.1 ISO images I have previously downloaded.
The next thing that happens is bittornado analyzes the existing files, works out which chunks are corrupt, downloads those chunks, and repairs the corrupted ISO images. Total bytes downloaded: approximately 512K - a saving of almost 1.2G. Where I come from we call that "not too shabby", or possibly we call it "Fred", depending on whether we've taken our medication.