Jan. 19, 2011
4:22 p.m.
On 19/01/11 8:48 AM, Schwab,Wilhelm K wrote:
Sig,
Are we discussing the same OS? What you are describing matches my experience on Windows; on Linux, AFAIK, one can just stomp all over the files and leave a mess. Perhaps something has changed to make it safer since I last trashed an image that way.
I agree that there are times when it does not matter, so any safety mechanism needs to be optional, or better yet tied to a development session vs. a deployed session.
Bill
I run a common .image file that is interpreted multiple times with a different start up script. There is no .changes file. This works on MacOSX and Ubuntu. This is the behaviour I want to have, so such a "safety mechanism" would definitely need to be optional. -- Yanni