A long, long, time ago (like 1998?) we (at Interval) did this. I can't find any code but IIRC we - saved image to temp.file - checked it worked - delete previous image file - rename temp to correct name
One might sensibly try checking if there is plenty of available room and skip the complexity when possible. Or one might create a null file with "at least enough room" (RISC OS made this especially simple) and then write into that. I'd guess that 'modern' file systems might well do annoying tricks like not actually creating the file when you think it has.
Real paranoiacs might want to to use OSProcess to start up the saved tempfile image and make sure it passes some tests before actually renaming etc.
On 2024-04-02, at 8:57 AM, Juan Vuletich via Vm-dev vm-dev@lists.squeakfoundation.org wrote:
I fully agree with Vanessa. Any such policy hardcoded in the VM will only limit the image choice on how to such backups.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: JTC: Jump To Conclusions