Harry Putnam <[email protected]> writes: >> >> Create a clone of the current environment and never touch it. > > Thanks for that reference to `copy on write (COW)'. This is my first > brush with those concepts which I am finding good discussion of with > google. I'll admit I don't fully understand it yet. > > But correct me if I have this wrong. > > The miss-named `clone', is not stand alone (Something one would > expect from a `clone'). That is, it relies still on the parent if > called into duty. Is that right? > > Could you move(mv) the clone to a new disc and boot it up? Or does > the COW kick in during mv... I'm not clear what happens. >
BZZZZZT => wrong: > Similar with the `snapshot'. It sounds like an OS frozen in time when > the shutter snapped. But can you move it to a new disc and boot up? On further consideration I need to drop this about snapshot.. After all, applying the term to real photographic snapshots, one would never expect a real snapshot to have the capabilities of the subject of the snap. So poor analagy... deeply flawed. But what about `clone'? It seems my reasoning stands on that. _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
