I'm not sure what motivated this wrapper. But Google landed me here and I gave it whir. Alas failed to be useful for me, as I need it primarily so I can rsync to and from my Windows box from another machine on the VPN I'm on. And the reason cited was, lacking --server support (as in rsycn complains of that. So clearly that is not a use case it was designed for. So I dropped it and went with Cygwin and that works totally fine. I can now rysnc to and from the windows box with syntax like:
rsycn -a mydir/ me@windowsbox:/cygdrive/c/users/me
rsycn -a me@windowsbox:/cygdrive/c/users/me/mydir/ .
That is, Cygwin's rsync doesn't see C:\ it maps it to /cygdrive/c/ and uses the / path separator not the \ separator.
Of course that requires you have keyed ssh access to the Windows box (which is the first thing to configure).
That left me suspecting one motivator for this wrapper might have been to support native Windows file paths and not this cygdrive recast. Which is fine, but not something I care about right now as I am using it mainly for in and out of the win box. On the box frankly I just use:
and that works for me. But inter machine rsync needs to be able to ssh in (keyed/passwordless) and run rsync --server. You can of course override this by specifying --rsync-path=PROGRAM as in --rsync-path=wsl rsync but I was keen for a default I guess of just rsync avoid the overhead of a wsl load. So here I am for now, with Cygwin.
I'm not sure what motivated this wrapper. But Google landed me here and I gave it whir. Alas failed to be useful for me, as I need it primarily so I can rsync to and from my Windows box from another machine on the VPN I'm on. And the reason cited was, lacking
--serversupport (as in rsycn complains of that. So clearly that is not a use case it was designed for. So I dropped it and went with Cygwin and that works totally fine. I can now rysnc to and from the windows box with syntax like:That is, Cygwin's rsync doesn't see
C:\it maps it to/cygdrive/c/and uses the/path separator not the\separator.Of course that requires you have keyed ssh access to the Windows box (which is the first thing to configure).
That left me suspecting one motivator for this wrapper might have been to support native Windows file paths and not this cygdrive recast. Which is fine, but not something I care about right now as I am using it mainly for in and out of the win box. On the box frankly I just use:
and that works for me. But inter machine rsync needs to be able to ssh in (keyed/passwordless) and run
rsync --server. You can of course override this by specifying--rsync-path=PROGRAMas in--rsync-path=wsl rsyncbut I was keen for a default I guess of justrsyncavoid the overhead of a wsl load. So here I am for now, with Cygwin.