public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: asaf greenberg <asafgreenberg@gmail.com>
To: cygwin@cygwin.com
Subject: Re: rsync from cygwin to linux adds characters in ascii files
Date: Thu, 19 May 2011 21:55:00 -0000	[thread overview]
Message-ID: <loom.20110519T231104-591@post.gmane.org> (raw)
In-Reply-To: <4DD530D9.3020202@gmail.com>

> When i rsync a folder from cygwin (winXP-SP3-32bit) to linux (64bit)
> some of the contents (e.g. in php files) are modified (e.g. added
> spaces, missing semicolon).
> 
> My local partition D:/ is (probably) mounted as binary.
> 
> D:\www\public>mount
> D:/programs/usr/bin on /usr/bin type ntfs (binary,auto)
> D:/programs/usr/lib on /usr/lib type ntfs (binary,auto)
> D:/programs/usr on / type ntfs (binary,auto)
> C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
> D: on /cygdrive/d type ntfs (binary,posix=0,user,noumount,auto)
> E: on /cygdrive/e type ntfs (binary,posix=0,user,noumount,auto)
> F: on /cygdrive/f type iso9660 (binary,posix=0,user,noumount,auto)
> 
> When I copy files with TAR, the files are identical to their source (of 
> course).
> 
> Is there  way to restrict RSYNC to run on binary mode?
> 
> thanks!


additional note: my rsync version is
rsync  version 3.0.7  protocol version 30
local filesystem: ntfs
remote system: Linux heze 2.6.32.8-grsec-2.1.14-modsign-xeon-64 #2 SMP x86_64
GNU/Linux
remote mount type: /dev/sdb1 on /home type ext3
(rw,nosuid,nodev,noatime,nodiratime,errors=remount-ro,data=writeback)


thanks again

asaf greenberg <asafgreenberg <at> gmail.com> writes:



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2011-05-19 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 13:57 asaf greenberg
2011-05-19 21:55 ` asaf greenberg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20110519T231104-591@post.gmane.org \
    --to=asafgreenberg@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).