Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com To: cygwin@cygwin.com From: Alejandro Lopez-Valencia Subject: Re: Pserver on cygwin corrupts binary files Date: Wed, 18 Feb 2004 06:49:33 -0500 Organization: House of Cuckoo Lamasery Lines: 16 Message-ID: References: <00d101c3f583$8a14dd90$6500a8c0@Ray> <00d601c3f586$d59e25c0$6500a8c0@Ray> <20040218100109.GG18953@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org Keywords: Has control X-Headers X-Gmane-NNTP-Posting-Host: plms16750-234.pool.007mundo.com X-Archive: encrypt Mail-Copies-To: never X-Newsreader: Forte Agent 2.0/32.640 On Wed, 18 Feb 2004 11:01:09 +0100, Corinna Vinschen wrote in <20040218100109.GG18953@cygbert.vinschen.de>: >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 Thanks for ether correction. But wasn't that the case a couple of years back? -- 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/