Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
list-help:	<mailto:cygwin-apps-help AT sourceware DOT cygnus DOT com>
list-post:	<mailto:cygwin-apps AT sourceware DOT cygnus DOT com>
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-apps AT sourceware DOT cygnus DOT com
Sender:	corinna AT snoopy DOT vinschen DOT de
Message-ID:	<395B2EEF.B305E0EF@cygnus.com>
Date:	Thu, 29 Jun 2000 13:11:43 +0200
From:	Corinna Vinschen <vinschen AT cygnus DOT com>
Reply-To:	cygapp <cygwin-apps AT sourceware DOT cygnus DOT com>
X-Mailer:	Mozilla 4.73 [en] (X11; I; Linux 2.2.14 i686)
X-Accept-Language:	de, en
MIME-Version:	1.0
To:	Chris Faylor <cgf AT cygnus DOT com>
CC:	cygwin-apps AT sourceware DOT cygnus DOT com
Subject:	Re: Pending change to cygwin DLL and binmode/textmode musings
References:	<20000624234013 DOT A29970 AT cygnus DOT com>

Chris Faylor wrote:
> text mode and bin mode mounts in Cygwin.  My implementation gives precedence
> to the (little used?) _fmode variable which has always been around in Cygwin.
> Setting this variable to O_BINARY used to be the same as CYGWIN=binmode,
> i.e., it didn't affect disk files.  Now it does.

FWIW, I'm _heavily_ interested in your incorporating that patch
into the developer sources. The reason is, I would be able to
speed up porting OpenSSH-2.1.1p1 by means. I would like to set
_fmode = O_TEXT and use O_BINARY where appropriate so I could
remove each use of `fopen(..., "rt")'. But: Wouldn't the use of
_fmode = O_TEXT additionally affect writes? I would still need the
differing of read (O_TEXT) and write (don't care).

Corinna

-- 
Corinna Vinschen
Cygwin Developer
Cygnus Solutions, a Red Hat company

- Raw text -