ISOs, fetching,for Linux and BSD, et al.
Straight_Man
Geeky, in my own wayNaples, FL Icrontian
This is kind of a tech note, and might make for a sticky if admins so choose.
There are some rules for grabbing ISOs, and I will outline them here:
First, never stream multiple downloads from multiple servers for an ISO download. You can get different versions of same named ISO (see below for some reasons concerning how and why this can happen), or hit one server that is actually in sync stage where an admin or sync script has not locked the file actively being put on mirror, and will get a mess that way.
Second,it is possible for a bit error in a critical file to occur in transit as mirror grabs from master ISO being uploaded or as you download and for the result to be an invalid ISO after you burn it at your end, or for a mirror to calc a checksum (md5sum) and compare to an md5sum file that was corrupted or made in error, get a good md5sum 256 bit check result, and have an invalid ISO on a mirror.
So, if you get a bad install, look for two things:
First, see if files you get that do not work have been updated by your distro publisher, and apply updates. IF you get a ISO set that results in a bad kernel that panics totally as happened to Neverex, try a different mirror for that first ISO in set for your O\S. If you know the distro's main mirror, you might have to go to that mirror to get a good first ISO, which is the data that at minimum has kernel build stuff on it.
Second, go back to main distro mirror and grab and compare the md5sum file on that mirror with the md5sum file on mirror you first downloaded your ISO set from.
That brings me to third rule-- ALWAYS md5sum ISOs, and if any discrepancy TRASH ISO that is not checking and redownload, if possible from amirror that is more a main mirror for the distro involved. If a distro has md5sums published, and you gat an md5sum check failure, diff (compare byte by byte or character by character) the two files and if out of sync let the distro folks know what mirror or mirrors have bad md5sum files versus distro's md5sum calcs from their master files. If many mirrors have bads in common, they will probably groan and repush the files manually that do not check, so tell them what md5sums do not match also. They may also thank you indirectly, I have gotten burned ISO sets free that are fully registerable once doing this, and access to things not normally given to newbies to a distro also in some cases.
John.
There are some rules for grabbing ISOs, and I will outline them here:
First, never stream multiple downloads from multiple servers for an ISO download. You can get different versions of same named ISO (see below for some reasons concerning how and why this can happen), or hit one server that is actually in sync stage where an admin or sync script has not locked the file actively being put on mirror, and will get a mess that way.
Second,it is possible for a bit error in a critical file to occur in transit as mirror grabs from master ISO being uploaded or as you download and for the result to be an invalid ISO after you burn it at your end, or for a mirror to calc a checksum (md5sum) and compare to an md5sum file that was corrupted or made in error, get a good md5sum 256 bit check result, and have an invalid ISO on a mirror.
So, if you get a bad install, look for two things:
First, see if files you get that do not work have been updated by your distro publisher, and apply updates. IF you get a ISO set that results in a bad kernel that panics totally as happened to Neverex, try a different mirror for that first ISO in set for your O\S. If you know the distro's main mirror, you might have to go to that mirror to get a good first ISO, which is the data that at minimum has kernel build stuff on it.
Second, go back to main distro mirror and grab and compare the md5sum file on that mirror with the md5sum file on mirror you first downloaded your ISO set from.
That brings me to third rule-- ALWAYS md5sum ISOs, and if any discrepancy TRASH ISO that is not checking and redownload, if possible from amirror that is more a main mirror for the distro involved. If a distro has md5sums published, and you gat an md5sum check failure, diff (compare byte by byte or character by character) the two files and if out of sync let the distro folks know what mirror or mirrors have bad md5sum files versus distro's md5sum calcs from their master files. If many mirrors have bads in common, they will probably groan and repush the files manually that do not check, so tell them what md5sums do not match also. They may also thank you indirectly, I have gotten burned ISO sets free that are fully registerable once doing this, and access to things not normally given to newbies to a distro also in some cases.
John.
0
Comments
My name is ENVEREX and there was nothing wrong with any of the ISO images I downloaded, just simply that none of the kernels were compiled to support the Highpoint 372N controller.
MUAaahahaAA!!!!11!