Subject: Re: one byte reads in bash
From: Christopher Faylor <[email-masked]>
To: John Berthels <[email-masked]>
Cc: [email-masked]
Date: Thu, 12 Jun 2003 11:20:54 -0400

Please check out the project web page for links to available information
and ports:  http://cygwin.com/ .

If you don't see what you need there, then the cygwin mailing list is
the best place to make observations or get questions answered.
Information on the mailing list is available at the project web page.

For your convenience, I've reset the Reply-To: address to point to the
cygwin mailing list.  I've also Cc'ed this reply there.

On Thu, Jun 12, 2003 at 10:17:57AM +0100, John Berthels wrote:
>Hi folks,
>
>Sorry to bother you, but I've come across the same problem you discussed
>on 4th Sept 2002 in:
>
>http://www.cygwin.com/ml/cygwin/2002-09/msg00146.html
>
>i.e. bash reads script files a byte at a time. This appears to happen even
>on script files on a local disk, but it obviously hurts more on a network
>share.
>
>I'm doing the following:
>
>create a simple foo.sh file:
>
># Enough bytes to see the difference properly
># Enough bytes to see the difference properly
># Enough bytes to see the difference properly
># Enough bytes to see the difference properly
># Enough bytes to see the difference properly
># Enough bytes to see the difference properly
># Enough bytes to see the difference properly
>echo hoo
>
>
>save as 'foo.sh' on a local disk or network share and then:
>
>strace -o sh.strace sh foo.sh
>strace -o bash.strace bash foo.sh
>
>grep readv sh.strace bash.strace | less
>
>and see the true horror....
>
>
>I've grabbed the latest bash sources from a mirror of gnu.org and they
>still seem to have the #ifdef code you mentioned.
>
>I yet haven't tried a locally-built bash with your suggested fix in since
>we don't have gcc in our cygwin environment here (for odd and complex
>reasons involving out of date home-brew configure scripts) but I'll try
>and put something together if I can.
>
>
>
>Other than build a local bash.exe, what can I do to try and get this fixed
>in an official cygwin distro? [I looked at the 'bashbug' tool, but thought
>I'd check with you two first.]
>
>
>Thanks for any advice or comments (should I post this to the list? I'm not
>subscribed...)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/