Difference between revisions of "Check a Downloaded ISO Image For Errors"
Check a Downloaded ISO Image For Errors (view source)
Revision as of 15:15, 20 October 2012
, 11 years agono edit summary
imported>Verityproductions |
imported>Verityproductions |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
[[File:BigManjaroIcon.png|left|90px]] | |||
Prior to burning your downloaded ISO image (or using it as a virtual disc in Virtualbox), it is '''strongly''' recommended that you first check that it hasn't been corrupted. The consequences of not doing so - especially if you intend on installing Manjaro as your main operating system - should be obvious (i.e. a corrupted image will result in a corrupted installation). | Prior to burning your downloaded ISO image (or using it as a virtual disc in Virtualbox), it is '''strongly''' recommended that you first check that it hasn't been corrupted. The consequences of not doing so - especially if you intend on installing Manjaro as your main operating system - should be obvious (i.e. a corrupted image will result in a corrupted installation). | ||
| Line 13: | Line 15: | ||
The 'sha' part of the checksum file name stands for <u>S</u>ecure <u>H</u>ash <u>A</u>lgorithm. This algorithm is used to generate a particular code unique to the downloaded ISO image. '''sha1''' and '''sha256''' are different versions of the algorithm that you can use to do this. Whilst sha1 is the most commonly used version, sha256 is a later and more secure version. Which you decide to use is entirely your choice. '''However, if you are unsure, then it is recommended to use sha256'''. | The 'sha' part of the checksum file name stands for <u>S</u>ecure <u>H</u>ash <u>A</u>lgorithm. This algorithm is used to generate a particular code unique to the downloaded ISO image. '''sha1''' and '''sha256''' are different versions of the algorithm that you can use to do this. Whilst sha1 is the most commonly used version, sha256 is a later and more secure version. Which you decide to use is entirely your choice. '''However, if you are unsure, then it is recommended to use sha256'''. | ||
The checksum file itself is just a text document that contains | The checksum file itself is just a text document that contains a code that should match the code generated by the sha1 or sha256 algorithm. As such, if the code generated from the ISO file matches that contained in the checkum file, then the ISO is fine. Otherwise - if the two codes don't match - then it means that the ISO file has changed in some way, most likely due to being corrupted. You can think of it like someone using a secret password to identify who they are: if they provide the wrong password, then something is obviously amiss! | ||
Don't worry if this all sounds a bit much - it's actually very straightforward and easy to use! | Don't worry if this all sounds a bit much - it's actually very straightforward and easy to use! | ||
| Line 20: | Line 22: | ||
= Checking in Linux = | = Checking in Linux = | ||
To check the integrity of your downloaded file, it will be necessary to first open the downloaded checksum file using a text editor such as ''Gedit''. Depending on whether you intend to use sha1 or sha256, ensure that you have downloaded and opened the appropriate checksum file (i.e. ending in -sha1.sum or sha256.sum, respectively) as they will contain different codes. Once the checksum file has been opened - and the code is visible - open up your terminal and change to the directory where your downloaded ISO is stored. For example, if your ISO file is located in the default ''Downloads'' folder, you would enter the following command: | To check the integrity of your downloaded file, it will be necessary to first open the downloaded checksum file using a text editor such as ''Gedit''. Depending on whether you intend to use sha1 or sha256, ensure that you have downloaded and opened the appropriate checksum file (i.e. ending in -sha1.sum or -sha256.sum, respectively) as they will contain different codes. Once the checksum file has been opened - and the code is visible - open up your terminal and change to the directory where your downloaded ISO is stored. For example, if your ISO file is located in the default ''Downloads'' folder, you would enter the following command: | ||
cd Downloads | cd Downloads | ||
| Line 33: | Line 35: | ||
For example, the following command will use sha256 generate a code from the 64 bit Manjaro XFCE 0.8.1 ISO. The code generated can then be compared | For example, the following command will use sha256 generate a code from the 64 bit Manjaro XFCE 0.8.1 ISO. The code generated can then be compared to the code provided by the appropriate sha256 checksum file: | ||
sha256sum manjaro-xfce-0.8.1-x86_64.iso | sha256sum manjaro-xfce-0.8.1-x86_64.iso | ||