Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 4 Sep 2002 23:07:28 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: BASH slow on network share scripts (was RE: A Simple Real World Benchmark for cygwin) Message-ID: <20020905030728.GB10427@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20020904112249 DOT D1213 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Wed, Sep 04, 2002 at 11:44:52PM +0200, Dan Vasaru wrote: >Since CYGWIN seems to go to some length to allow O_TEXT seeking, I believe >the ifdef above to be a remnant of some times where cygwin1.dll didn't >support text seeks, and I propose to remove it. You're probably right, but since most scripts (such as configure scripts) are usually interpreted by /bin/sh, which is ash, not bash, then this shouldn't have much impact on the normal running of scripts. Unless, of course, there are similar problems in ash. Still, it would be very nice to get this fixed in bash. >I don't know who to contact on this issue, so someone please notify the >current bash-cygwin maintainer ? You can always check cygwin-announce to find this info, but, really, you shouldn't have to do that. Sending email here is the proper way to deal with the issue. Sending personal email to a package maintainer should be the absolute last resort. Public discussion is good. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/