@Marc2 Probably yes and no… and it depends on when you do the checksum…
If you are using FOG’s early hostname change, then a simple changing of the name on the OS disk would totally change the checksum. Booting the computers before the comparison is likely to totally change the checksum. The checksum must be done before namechange and before boot.
This means you’d have to either schedule a shutdown after imaging and then boot to a linux live CD and do the checksum test, or, do a debug deployment and cancel the process right at the early host name change point and manually do the checksum during debug (which has very limited commands and you’d probably need to install some utilities right then and there) and then proceed to manually finish the imaging process via command line.
I found this post on another site:
But it depends on the layer you define “same”
For this answer I assume/dev/sdb1 and /dev/sdc1 are the ones you want to compare both partitions are not mounted if they are mounted, you have the permission to read each file
You can test the two partitions on blocklevel.
But for this to produce the same hash, the partitons have to be exactly the same.
Even the slightest change in one of the files in either of the two,
will produce a different hash.
You can also test on filelevel.
There are probably already tools, that could be used for your purposes (tripwire maybe?),
but a quick-and-dirty solution can be this: