[<<]Message[>>]    [<<]Author[>>]    [<<]Subject[>>]    [<<]Thread[>>]

Number   :  10808
Date     :  2005-03-18
Author   :  Kan Yabumoto
Subject  :  Re: XXKILL
Size(KB) :  3


Garry wrote:

>--- In xxcopy@yahoogroups.com, Kan Yabumoto  wrote:
> > Hi, all:
> >
> > We just learned a sad episode from a user who call our
> > product, XXKILL. An interesting name.
>
> >> I strongly suggest you build in a stronger, interactive
> >> warning for /CLONE:
> >>
> >> "All files/directories in the target folder will be DELETED!!!!!!
> >> - - ARE YOU ABSOLUTLY SURE??"
> >>
> >> INSTEAD of the warning at the beginning that says something
> >> like "verify the target directory, is it correct?".
> >>
> >> what could be called a _very very mild_ warning, that does
> >> say nothing about the consequences!!
>
>For a number of reasons, I can't agree with Mic's suggestion
>for an extra level of prompting but I do agree that the
>current prompt could be more forceful. Here's my suggestion:
>
>Warning: make sure the Destination (........) is correct.
>This command will delete extra files/dirs in the destination!
>Press Ctrl-C to abort, any other key to begin deleting/copying file
>(s).
>
>Garry

As usual, my earlier message follows our typical response
in such cases --- justification and defense of the current
scheme.

I guess the current scheme (as to the frequency and the
way the implicit /PZ switch works) is very close to the
optimum except that we could add the description of the
adverse consequence. Apparently, the problem is that those
who use the /CLONE command and lose all the files do not
know what the hell they are doing. That is, they learn
the /CLONE command from somewhere (typically a terse
recommendation in newsgroups).

We describe /CLONE as a directory duplication feature.
I remain adamant that a clone operation must remove
extra files/directories from the destination. If the
operation preserves extra files in the destination,
the source and the destination are not logically
equivalent, therefore, the destination is not a faithful
duplicate of the source. That's how I perceive a CLONE.

Regardless of the correctness (or otherwise) of the
definition of Cloning, for those who have a totally
different expectation from the operation will be at risk.

So, we will change the wording like what Garry suggests.

##### WARNING!!! ##### WARNING!!! ##### WARNING!!! ##### WARNING!!! #####
Make sure Source (C:\xxxxx) and Destination (D:\xxxxx) are correct.
This command will delete extra files/directories in the destination!
Press Ctrl-C to abort, any other key to begin deleting/copying file(s).



We will also show the source name whose misspelling could play
an equally important role in the loss of files the destination.
Adding the source directory name in the first line would wrap
the line. So, the word "Warning" will be pushed up to a line
of its own. If we have a line for warning, might as well,
make it more threatening. To make it more obnoxious, we will
capitalize them. Oh, yes, the triple exclamations make it louder.
Might as well, the repeated pound-sign (####) should remind the
barbwire of a death camp. How about that.

Although it is not as tasteful as we would like, if it helps
reduce accidents, why not?

I hope this will not trigger a wholesale revision of all other
warning messages...

Kan Yabumoto



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.