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

On Fri, May 06, 2005 at 06:52:15AM -0700, Brian Dessent wrote:
>Eric Blake wrote:
>
>> Predefining O_BINARY as the default input_flags and output_flags is a
>> stopgap measure.  While it is fine for other programs, such as od, to
>
>Doesn't that overly complicate things?  Seems to me that whenever you
>use dd you are interested in copying fixed record length data.  It just
>doesn't seem very likely that you would actually ever want dd to operate
>in text mode.

I was going to make the same observation but then I read the dd man page
and saw that it was already capable of padding newline-terminated records
so I guess this wouldn't be that big a stretch.

It certainly shouldn't do this by "default", though, no matter what the
underlying mount says.

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/