On Friday 04 June 2010, Darwin Gregory wrote:
> If you execute "cp /path/*" the command expands the wildcard, and treats
> the last file as the destination directory. If the last file in /path/ is
> not a directory the command fails, but not with the appropriate error.
> However, if the last
Darwin Gregory wrote:
> I did a quick search of the archive, and didn't find this one,
It gets discussed every so often. Look for file glob or file
globbing.
> but there seems to be a potential logical failure in the cp and mv
> commands. It may be specific to an implementation, but I feel it i
On 06/04/2010 10:13 AM, Darwin Gregory wrote:
> I did a quick search of the archive, and didn't find this one, but there
> seems to be a potential logical failure in the cp and mv commands. It may
> be specific to an implementation, but I feel it is a critical issue.
It is generic to how Unix wor
If you execute "cp /path/*" the command expands the wildcard, and
treats the last file as the destination directory.
That is at it should be, * is expanded by the shell, not by the command.
I did a quick search of the archive, and didn't find this one, but there
seems to be a potential logical failure in the cp and mv commands. It may
be specific to an implementation, but I feel it is a critical issue.
I have tested this on Suse Enterprise 10.x and OpenSuse 11.x (the only
implementa
