Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 18 Feb 2004 11:01:09 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Pserver on cygwin corrupts binary files Message-ID: <20040218100109.GG18953@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <00d101c3f583$8a14dd90$6500a8c0 AT Ray> <00d601c3f586$d59e25c0$6500a8c0 AT Ray> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i 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. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/