contents
<h2>What is Checksum for Linux?</h2>Checksum for Linux is a <a href="http://en.wikipedia.org/wiki/Bash_%28Unix_shell%29" title="in your terminal, do: man Bash" id="link-external-WikiPedia-Bash" target="_blank" rel="noopener noreferrer">Bash</a> script which attempts to emulate some of the most basic <a href="<?php echo $site_config['url']; ?>/windows/software/checksum/" title="checksum for Windows - where all the goddies are!" id="link-internal-checksum-for-windows-main-alpage" target="_blank" rel="noopener noreferrer">checksum</a>-like features, effortless recursion, synchronization, multihash™ support and such, with simple operation and nifty KDE/Gome GUI integration, something I needed for a time. Because it is a Bash script, you can run it directly from a console or script. And because it's Linux, you can run it on your <a href="http://en.wikipedia.org/wiki/Network-attached_storage" title="Network Attached Storage" id="link-external-wikipedia-NAS" target="_blank" rel="noopener noreferrer nofollow">NAS</a>.<p>The Linux version of checksum lacks many (most) of the Windows' version's coolest features. It has everything I needed, which is how checksum on Windows started, until I started thinking about it more, asking questions and answering <em>your</em> questions about it. More recently, people have started asking me about the Linux side of checksum, as the popularity of NAS boxes increases, I guess. So I've done more work on this since.<p>For now, you can grab a copy of the latest checksum for Linux zip, as well as check out the script itself (Note: I've added a <code>.sh</code> extension to these web files so the server knows what to do with them).<p>checksum recognizes the name of the symlink it was called from and switches to that mode, you see.<p>There are a couple of demo shortcuts and symlinks in there, too, for reference and inspiration. For more information, open the checksum script itself (<code>/usr/local/bin/checksum</code>) in a decent text editor, or click <code>checksum.sh</code>, above.<h3>2do..</h3><p>There is still a lot to be done. The verify output is poor in the console (it was designed to be run from my KDE desktop), in that it doesn't give a clear indication of failures at the end of the potentially long list of results, forcing the user to scroll, the scripter to parse.<p>;o)