Yes No. -exec is directly launching the "cp" command with its arguments. There is no ksh involved here.

Because the shell expands * and you have too many of them in the current directory.

In the "find" manual page and in the various web pages about it.

Because ';' is required to delimit the end of the -exec clause but ';' alone would be picked by the current shell as a command separator if not escaped by '\'.

Not sure, did you replace $1 and $2 by something useful ?

Absolutely. exec is a ksh builtin command while "-exec" is an unrelated find option.

---------- Post updated at 18:38 ---------- Previous update was at 18:36 ----------

It is needed to fulfill this requirement:

Code:

 # Does not cp hidden files

---------- Post updated at 18:41 ---------- Previous update was at 18:38 ----------

That's the other way around. There is an extra space between the backslash and the semicolon in your suggestion. That space is defeating the backslash requirement.