Thanks for checking this for me, apparently I've got hardware problems.
Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) . On Fri, 17 Mar 2023, Thomas Schmitt wrote: > Hi, > > Jude DaShiell wrote: > > https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-2.iso.sha256 > > https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-2.iso > > Let's see what an older Debian perceives (... downloading 3.7 GiB lasts a > while ...): > > $ sha256sum -c slint64-15.0-2.iso.sha256 > slint64-15.0-2.iso: OK > > Various checksums: > > $ sha256sum slint64-15.0-2.iso > cc0421fdd9630d3bb3ea8ef338c7cfb7a29fd8df98ccbae3debed60847a976a3 > slint64-15.0-2.iso > $ sha512sum slint64-15.0-2.iso > > faf3210c680caeb5875651989aeb2841b4a0733a618b8d13e5163ebf5c16046d82d4ee645d471664604eeb164e0bd7b919f64e4798167f48a6ed2e935d06d6a4 > slint64-15.0-2.iso > $ md5sum slint64-15.0-2.iso > f00a3d3bf641309feac4b1aa9abacf4f slint64-15.0-2.iso > $ crc32 slint64-15.0-2.iso > 3ed8c08a > $ > > I don't think that somebody fiddled with pickles like md5sum or crc32. > So only if sha256sum says mismatch and md5sum says match, then i would > suspect that sha256sum is broken. > > > Have a nice day :) > > Thomas > >
