X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Changed handling of "!" in /bin/sh? Date: Wed, 17 Jan 2007 18:14:27 -0500 Message-ID: <31DDB7BE4BF41D4888D41709C476B657041696A9@NIHCESMLBX5.nih.gov> In-Reply-To: <45AD9572.8000905@byu.net> References: <20070117015312 DOT 43811842EF AT pessard DOT research DOT canon DOT com DOT au> <45AD9572 DOT 8000905 AT byu DOT net> From: "Buchbinder, Barry \(NIH/NIAID\) [E]" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l0HNEfom012517 Eric Blake wrote on Tuesday, January 16, 2007 10:18 PM: > According to Luke Kendall on 1/16/2007 6:53 PM: >> >> Or, copy /bin/ash.exe to replace /bin/sh.exe. > > Not recommended. The reason cygwin moved to bash as > /bin/sh was to avoid ash bugs. I thought that it was more to avoid all the complaints that sh did not behave like bash, which is what many people expected. - Barry -- 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/