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 Message-Id: <4.3.1.2.20010117164325.026dcd88@pop.ma.ultranet.com> X-Sender: lhall@pop.ma.ultranet.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 17 Jan 2001 16:50:21 -0500 To: frank.palazzolo@autodesk.com, cygwin@cygwin.com From: "Larry Hall (RFK Partners, Inc)" Subject: RE: Cygwin commands crashes after ssh login In-Reply-To: <258E47267E4BD3118DCA00805FA72E08052AF425@hqmsgsrf03.autode sk.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 04:42 PM 1/17/2001, frank.palazzolo@autodesk.com wrote: > >/bin/sh is bash in the standard gnu dist.. :-) So copy your compiled > >bash to /bin/sh.. > > > > /Andy > >Thanks Andy, > >That's what I thought too, but when the file sizes were so different I looked around and realized my sh.exe came from ash-20001002.tar.gz, which is a different shell and codebase, I guess. Absolutely. In Cygwin /bin/sh is NOT equivalent to /bin/bash. /bin/sh is ash, which is an optimized version of the bourne shell. Its used instead of bash for performance reasons (mostly noticeable in configures). However ash does seem to have more bugs than bash (if the issues that arise on this list are any indication). While the bugs that have been found have been rapidly fixed, how many are left is uncertain (as always). If shell performance is not you're major concern, you can use bash as /bin/sh. However, recompiled or not, any version of bash is different enough from ash to have a strong potential for reacting differently in any particular case. Usually this means its more forgiving/works better. YMMV. Larry Hall lhall@rfk.com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple