From: cgf AT cygnus DOT com (Christopher Faylor)
Subject: Re: Answer to your text == binary question
22 Jan 1999 05:51:46 -0800
Message-ID: <19990122082603.A25347.cygnus.cygwin32.developers@cygnus.com>
References: <3 DOT 0 DOT 5 DOT 32 DOT 19990121172155 DOT 0080c6a0 AT pop DOT ne DOT mediaone DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: Geoffrey Noer <noer AT cygnus DOT com>
Cc: cygwin32-developers AT cygnus DOT com,
        "Pierre A. Humblet" <Pierre DOT Humblet AT eurecom DOT fr>

On Thu, Jan 21, 1999 at 11:54:33PM -0800, Geoffrey Noer wrote:
>> I thought that since the automounts exist in the mount table, that
>> the binmode status of the automount would be the logical way to
>> control this.
>
>I meant using binmode status of the CYGWIN env variable to determine
>what binmode to associate with the automounts.  The status would be
>stored in the same flags area as text or binmode for normal mounts.
>The problem is that since the user isn't choosing whether or not to
>add an automount, it's not possible for them to specify binmode in the
>standard way (an argument to the mount command).
>
>(Maybe I'm not understanding you?)

I thought that we agreed that the default would be text mode mounts.  If
the user wants to change that then they override it by specifying -b to
the mount command along with whatever option is required to specify the
automount directory.  Then files opened using /mycygdrive will have
whatever mode the user wants.

That leaves CYGWIN=[no]binmode as the method for specifying the CRLF
translation for devices and, possibly, std file handles inherited from
the command shell.  That was my intent when I implemented this feature.
Although, now that I think of it, you can override devices with the
mount command, too.

cgf