Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date:	Wed, 26 Apr 2000 21:19:54 -0400
Message-Id:	<200004270119.VAA24969@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	khan AT NanoTech DOT Wisc DOT EDU
CC:	cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to:	<200004261944.OAA13998@hp2.xraylith.wisc.edu> (message from Mumit
	Khan on Wed, 26 Apr 2000 14:44:47 -0500)
Subject:	Re: hybrid text/binary mount
References:	<200004261944 DOT OAA13998 AT hp2 DOT xraylith DOT wisc DOT edu>

> That was the caveat I was pointing out as well -- better the devil
> you ... At least we can now control the behaviour in two predictable
> ways -- mount and explicit binary/text mode I/O.

How about, instead of "auto" we call it "mixed" - read in text mode,
write in binary mode?  A text-mode read will handle unix-style text
files properly anyway, but we won't need that complex detection code.

- Raw text -