X-Spam-Check-By:	sourceware.org
From:	ericblake AT comcast DOT net (Eric Blake)
To:	Sven Severus <s DOT severus AT hima DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Why binary mode?
Date:	Fri, 23 Feb 2007 00:30:16 +0000
Message-Id:	<022320070030.27766.45DE3598000BA38700006C7622007358340A050E040D0C079D0A@comcast.net>
X-Mailer:	AT&T Message Center Version 1 (Oct 4 2006)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

> This is, what I expect, after reading the Cygwin FAQ:
> "When processing in text mode, [...] written to the file [...] 
> you in fact get "Hello\r\n". Upon reading this combination, 
> the \r is removed [...]".
> Why is it in fact not removed when reading with cat?

The FAQ is outdated.  Would you care to volunteer to help
maintain it?  Reading the NEWS for coreutils, cat was changed
upstream in the last two years or so to always be binary-only,
to more closely comply with POSIX rules that state that
cat must operate on all file types, not just text files.
If cat used default mode, it would corrupt true binary
files that lived in text mounts.

-- 
Eric Blake
volunteer cygwin coreutils maintainer

--
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/

- Raw text -