Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Sun, 4 Jun 2000 17:32:08 +0400 From: Egor Duda X-Mailer: The Bat! (v1.41) Reply-To: Egor Duda Organization: DEO X-Priority: 3 (Normal) Message-ID: <3730.000604@logos-m.ru> To: cygwin-dev Subject: Re[2]: text / binary mounts (sorry) In-reply-To: <20000602214630.B3577@cygnus.com> References: <20000602214630 DOT B3577 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Saturday, 03 June, 2000 Chris Faylor cgf AT cygnus DOT 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. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19