Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <1DB8BA4BAC88D3118B2300508B5A552CD92550@mail.fitlinxx.com> From: David Bolen To: "'cygwin AT sourceware DOT cygnus DOT com'" Subject: RE: text / binary mounts (sorry) Date: Fri, 2 Jun 2000 17:35:29 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Earnie Boyd [earnie_boyd AT yahoo DOT com] writes: > Are you sure of this, Ron? AFAIK CYGWIN=binmode only affects the pipes and > redirection and not file I/O. BTW CYGWIN=binmode is the default. One minor caveat with respect to "default" - the default behavior for the stdin/stdout handles changed from b20.1 to the net releases, dependent on whether you explicitly had the environment variable or not. If you put CYGWIN=binmode in your environment it also affects stdin/stdout default behavior, but if you leave the variable out they will default to text mode and not binary. It's my understanding this was done for some issues with interactive tool use, but unfortunately it also comes into play when utilities fork() a copy of themselves to process data on stdin/stdout (I ran into this with the rsync utility). The precise "better" default behavior is arguable, but at a minimum it's just something to be aware of if you are running without CYGWIN=binmode in your environment. -- David /-----------------------------------------------------------------------\ \ David Bolen \ E-mail: db3l AT fitlinxx DOT com / | FitLinxx, Inc. \ Phone: (203) 708-5192 | / 860 Canal Street, Stamford, CT 06902 \ Fax: (203) 316-5150 \ \-----------------------------------------------------------------------/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com