Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 6 May 2005 10:39:53 -0400
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: DD converts LF -> CR / LF
Message-ID: <20050506143953.GB20565@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
References: <427B1A65.5060106@tu-bs.de> <427B258F.90516ACA@dessent.net> <427B70CB.7040101@byu.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <427B70CB.7040101@byu.net>
User-Agent: Mutt/1.5.8i

On Fri, May 06, 2005 at 07:27:39AM -0600, Eric Blake wrote:
>There is still the question on cygwin whether an unspecified
>text/binary mode should always default to binary, or should default to
>the underlying default for that particular mount.

I think that dd should always default to binary unless directed not to
do so.  I don't think anyone would be expecting it to perform automatic
LF->CRLF translations for them since that is not a documented feature of
the utility.

>Meanwhile, I noticed that cygwin permits open("foo", O_RDWR | O_BINARY
>| O_TEXT), although I don't know which of the two modes it chose; I
>think it should instead return EINVAL like setmode(fd, O_BINARY |
>O_TEXT) does.

This behavior is consistent with windows, AFAICT.

cgf

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