* overview2.sgml: Remove CTRL-Z discussion.

* cygwinenv.sgml: Expand on CYGWIN=binmode.

winsup/doc/ChangeLog

@@ -1,3 +1,8 @@
+2002-12-18  Christopher Faylor  <cgf@redhat.com>
+
+	* overview2.sgml: Remove CTRL-Z discussion.
+	* cygwinenv.sgml: Expand on CYGWIN=binmode.
+
 2002-11-10  Christopher Faylor  <cgf@redhat.com>
 
 	* how-programming.texinfo: Document _WIN32 more fully.

winsup/doc/cygwinenv.sgml

@@ -10,9 +10,15 @@ by prefixing with <literal>no </literal>.</para>
 <listitem>
 <para><FirstTerm>(no)binmode</FirstTerm> - if set, non-disk 
 (e.g. pipe and COM ports) file opens default to binary mode 
-(no CR/LF/Ctrl-Z translations) instead of text mode.
-Defaults to set (binary mode). This option must be set
-before starting a Cygwin shell to have an effect on redirection.
+(no CRLF translation) instead of text mode.  Defaults to set (binary
+mode).  By default, devices are opened in binary mode, so this option
+has little effect on normal cygwin operations.
+
+It does affect two things, however.  For non-NTFS filesystems, this
+option will control the line endings for standard output/input/error
+for redirection from the Windows command shell.  It will also affect
+the default translation mode of a pipe, although most shells set the
+pipe to binary by default.
 </para>
 <warning><title>Warning!</title><para>If set in 12/98 b20.1, all files 
 always open in binary mode.</para></warning>

winsup/doc/overview2.sgml

@@ -171,9 +171,7 @@ sources.</para>
 
 <para>Unfortunately, UNIX and Win32 use different end-of-line terminators in
 text files.  Consequently, carriage-return newlines have to be translated on
-the fly by Cygwin into a single newline when reading in text mode.  The
-control-z character is interpreted as a valid end-of-file character for a
-similar reason.</para>
+the fly by Cygwin into a single newline when reading in text mode.</para>
 
 <para>This solution addresses the compatibility requirement at the expense of
 violating the POSIX standard that states that text and binary mode will be