How to generate identically image file after snapshots

Boris Popov boris at deepcovelabs.com
Mon Jul 30 15:50:52 UTC 2007


cp image.im twinbrother.im

;)

-Boris

-- 
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

boris at deepcovelabs.com

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

> -----Original Message-----
> From: squeak-dev-bounces at lists.squeakfoundation.org
[mailto:squeak-dev-
> bounces at lists.squeakfoundation.org] On Behalf Of Martin Troielli
> Sent: Monday, July 30, 2007 8:32 AM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: How to generate identically image file after snapshots
> 
> Hi All,
> 
> We have tried to produce the same (bit identically) image file after
two
> consecutive snapshots. We start from a base image then, fileIn several
> files into it and finally, we just SmalltalkImage current snapshot:
true
> andQuit: true. We need this to verify the image file generated by a
> third-party with a checksum by executing a script.
> After trying several ways to get it (even by scripting the fileIn
process
> and the snapshot), we found that the image files have, beside the
> timestamp differences, thousands of other differences and sometimes
the
> snapshots have also size differeces.
> We supose that this kind of issues may occur due to the GC activity.
> Are this issues from the way GC process is changing dynamically the
memory
> bytes? There is a way to inhibite this activity?
> Attached are the scripts we use to produce the image files.
> 
> Many thanks in advance,
> Martin Troielli



More information about the Squeak-dev mailing list