This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: text / binary mounts (sorry)
- To: cygwin-dev <cygwin-developers at sourceware dot cygnus dot com>
- Subject: Re: text / binary mounts (sorry)
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Sun, 4 Jun 2000 18:29:27 -0400
- References: <20000602214630.B3577@cygnus.com> <3730.000604@logos-m.ru>
- Reply-To: cygwin-developers at sourceware dot cygnus dot com
On Sun, Jun 04, 2000 at 05:32:08PM +0400, Egor Duda wrote:
>Saturday, 03 June, 2000 Chris Faylor cgf@cygnus.com wrote:
>CF> On Fri, Jun 02, 2000 at 04:41:27PM -0500, Parker, Ron wrote:
>>>> Since the //h usage is deprecated, I'm not going to worry too
>>>> much about this.
>>>
>>>The larger point, IMHO, is that, 'echo Hello>//machine/sharename/filename'
>>>also produces 7 bytes. This leads me to the question of, "How does one
>>>default UNC file access to binary mode?" I know it works if the UNC path is
>>>mounted and you access it via the mount point, but what should happen when
>>>going directly to the UNC path?
>
>CF> Right now, the same thing happens as has happened for the last three or
>CF> four years with cygwin. It defaults to text mode.
>
>btw, do you think there should be a way to control this. something
>like CYGWIN=filebinmode ? if yes, i'm ready to submit a patch.
>
>hmm, "filebinmode" seems a bit confusing, but don't see more
>descriptive word.
I'd rather not complicate the text mode logic right now. DJ is talking
about an improvement to cygwin that may change things for the better.
cgf