Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Fri, 2 Jun 2000 21:46:30 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: text / binary mounts (sorry) Message-ID: <20000602214630.B3577@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin@sourceware.cygnus.com References: <200006022142.OAA26463@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006022142.OAA26463@cygnus.com>; from rdparker@butlermfg.com on Fri, Jun 02, 2000 at 04:41:27PM -0500 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? Right now, the same thing happens as has happened for the last three or four years with cygwin. It defaults to text mode. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com