You have to cp the image once the engine interacts with it it is never the "same" lots of objects get created and destroyed in image start up the garbage collector runs anything using a clock runs. So if it is a script it has to be a shell script. Any deployment specific stuff should go in some config or text file that is read on start up.
Sean
-----Original Message----- From: squeak-dev-bounces@lists.squeakfoundation.org [mailto:squeak-dev-bounces@lists.squeakfoundation.org] On Behalf Of Martin Troielli Sent: Monday, July 30, 2007 8:32 AM To: squeak-dev@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