Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <40343882.2090904@cwilson.fastmail.fm>
Date: Wed, 18 Feb 2004 23:16:02 -0500
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Pserver on cygwin corrupts binary files
References: <00d101c3f583$8a14dd90$6500a8c0@Ray> <00d601c3f586$d59e25c0$6500a8c0@Ray> <c0u7cg$7gs$1@sea.gmane.org> <20040218100109.GG18953@cygbert.vinschen.de>
In-Reply-To: <20040218100109.GG18953@cygbert.vinschen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Corinna Vinschen wrote:
> On Feb 17 18:16, Alejandro Lopez-Valencia wrote:
> 
>>Because when using textmode, cygwin changes the semantics of I/O
>>functions in the underlying C runtime. It does (and forces) EOL
>>conversion on all files read and written to the filesystem as well as
>>*sockets* and *pipes* for all applications compiled with the runtime.
> 
> 
> Nope.  Sockets reads and writes are always binary.

The only problem is cvs has special code to do EOL munging itself.  I've 
tried to eliminate that cruft (or #ifdef it out) for the cygwin build, 
but I never tried to "certify" the pserver for use.  As far as I'm 
concerned, using the cygwin cvs as a pserver *server* is unsupported, 
although there have been rumors that it works.  For some people.  Under 
some (as usual, unspecified) conditions.

Of course, using cygwin cvs as a pserver *client* is always supported.

My point: to track down this issue will probably require getting dirty 
(e.g. tracing thru the code).

--
Chuck


--
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/