Hi, the miracle of staying or moving is decided by the alphabetic sequence of imported original and freshly made clone. This lets the files keep their old data storage address: -clone /hello/hello.world /hello/hello.z This causes data storage in the new session: -clone /hello/hello.world /hello/hello.clone
By a shortcomming of the static function iso_tree_clone_file() in libisofs/tree.c the cloned file is not marked as being imported from the loaded ISO, as is its original. This mark is important for the decision at image write time, whether a node can re-use its data storage or needs data storage in the new session. When the image production traverses the tree in alphabetic order it meets "hello.clone" before "hello.world" and decides the storage need of both by the missing import mark of "hello.clone". When it encounters "hello.world" before "hello.z", then it decides that no new storage is needed. Please verify this behavior with your local experiment. I plan to fix the bug in libisofs this evening. Have a nice day :) Thomas
