Strict Standards: Declaration of Doku_Renderer_metadata::table_open() should be compatible with Doku_Renderer::table_open($maxcols = NULL, $numrows = NULL, $pos = NULL) in /home/tinycore/wiki.tinycorelinux.net/inc/parser/metadata.php on line 24

Strict Standards: Declaration of Doku_Renderer_metadata::table_close() should be compatible with Doku_Renderer::table_close($pos = NULL) in /home/tinycore/wiki.tinycorelinux.net/inc/parser/metadata.php on line 24

Warning: Cannot modify header information - headers already sent by (output started at /home/tinycore/wiki.tinycorelinux.net/inc/parser/metadata.php:24) in /home/tinycore/wiki.tinycorelinux.net/inc/actions.php on line 180
wiki:md5sum - Tiny Core Linux Wiki

Welcome to the Tiny Core Linux Wiki at tinycorelinux.net!

Use md5sum to Check if a File has been Corrupted

If you download the Tinycore iso, or another file, you can check if it has been corrupted by verifying the md5sum.

To check the md5sum while running Tinycore or another Linux distribution, open the terminal and type:

cd path
md5sum name

For example if you had the file tinycore-4.5.6.iso in /home/tc/dl, you would type:

cd /home/tc/dl
md5sum tinycore-4.5.6.iso

Compare the md5sum generated, with the one on the site you downloaded Tinycore from.

In case of the example above, the output of the md5sum command should be:

3da0ad44a0f0603542d9e1034eca9d2d  TinyCore-4.5.6.iso

For our example, the reference value to compare with, will be in file http://distro.ibiblio.org/tinycorelinux/4.x/x86/archive/4.5.6/TinyCore-4.5.6.iso.md5.txt

If the md5sum is different, the file has been corrupted during the download.

To fix things, delete the corrupted file and try to download again.

Print/export