Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Fri, 20 Oct 2000 12:39:51 -0400 From: Christopher Faylor To: Cygwin Mailing List Subject: Re: Text vs. binary - should symlink be resolved? Message-ID: <20001020123951.C13677@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: Cygwin Mailing List References: <000101c03aac$097c4960$21c9ca95@mow.siemens.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <000101c03aac$097c4960$21c9ca95@mow.siemens.ru>; from Andrej.Borsenkow@mow.siemens.ru on Fri, Oct 20, 2000 at 07:40:13PM +0400 On Fri, Oct 20, 2000 at 07:40:13PM +0400, Andrej Borsenkow wrote: >Text vs. binary processing is based on whether file resides on binary or text >mounted filesystem. > >Currently Cygwin seems to check original filename as passed to open call. This >leads to interesting effect - symlink may point anywhere, and target may >reside on filesystem mounted with different option. > >IMHO the rule to determine open mode should be applied to symlink target >(final target) - after all, that is _the_ file itself. > >What do you think? I think that code speaks louder than words. :-) Send in a patch that makes things work the way you think they should work and I'll consider it. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com