not be able to read them but cp would? Seems like an odd restriction "rsync can read
and compare network paths, but can't actually open the paths to copy them because
it can't understand the paths that it created through it's own iteration.
2nd, how would half the files succeed/compare successfully after being copied via "cp".
Are you saying other linux commands have special processing in them to handle "//"? I've
just always assumed that was handled transparently by the cygwin path layer?
Rsync's handling of the paths is "inconsistent" with other utils under cygwin, thus the
reporting of it as a bug.
Christopher Faylor wrote:
On Thu, Dec 04, 2003 at 11:53:41PM -0800, linda w wrote:
Went to copy a dir:
rsync pooped all over the place:
law> rsync -avv --progress //ishtar/root/usr/src/packages/BUILD/dictd-1.4.9 /usr/src/packages/BUILD/
I doubt that rsync understands Windows '//' style paths.
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
