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 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15016.60551.581608.362225@jupiter.akutech-local.de> Date: Fri, 9 Mar 2001 15:45:27 +0100 From: Ralf Fassel To: Andrej Borsenkow Cc: Subject: Re: different behaviour of bash and sh In-Reply-To: References: <3AA8CFB3.4B515116@yahoo.com> Organization: Akustik Technologie Goettingen (ATG) * Andrej Borsenkow | So what? The question is, if the exibited behaviour of *sh* is | correct; the question was not "if sh is bash". Earnie wanted to point out that my report was inappropriate at the bash-bug mailinglist (which I had included since on my Linux systems /bin/sh is a link to /bin/bash, so I just assumed the two being identical on Cygwin too, which is not the case end of long sentence) | IMHO that is a bug in sh (or ash if you insist). The 'echo $?' is | the next command executed after 'false' - so , there is nothing that | can change the value of '$?' in between. For completeness sake: On my SUSE 7.1 System, `ash', `sh' and `bash' all echo `1', so I think this is really a problem in the cygwin port of `ash' which gets installed as /bin/sh. I just had a quick glance at the ash source, but I'm in for the weekend now, so no patches :-) R' -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple