X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:cc:subject:content-type
	:content-transfer-encoding:in-reply-to:references:date
	:message-id:mime-version; q=dns; s=default; b=RjSllj4ZV9gR14UP8w
	UGWWPLDdBxxTNVCI8VjGJlVVV99q6ZtSatTCzGDmSvPg54sJtvQukiznDYeJCm61
	qqH1QUBuKEksqnbqKS5ybgedfzaw/N1fVOAMx/I57NGConxVWz0TAQ2PDVhHbA23
	XtzAS0eE15z6OE/T7CfW3fyS4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:cc:subject:content-type
	:content-transfer-encoding:in-reply-to:references:date
	:message-id:mime-version; s=default; bh=yBXJ0N5WM5DOcRYqYiRjjU6I
	Neo=; b=xKSgjQs6gzKpZG0Lgw1k/c1Cb4PNh+fh34MW9YYtDYKPOa0FtoJOWvOk
	s9+aCI23AJ04lw9+84zYf1T3O9BczybPnHWd9l4SVKF5rTk9o0myl/rU3NcDDWvx
	Mt9vabSA6GJICDQJ9x8Y0z6eXb4n/udWtyMD1UezfSj6jkHCHZY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=HCc:U*cygwin, Hx-languages-length:899, H*i:sk:57027D5, H*f:sk:57027D5
X-HELO: mailout.ish.de
X-Abuse-ID: hremUFXL0y-8240 AT umkbw DOT customer
From: Helmut Karlowski <helmut DOT karlowski AT ish DOT de>
To: cygwin AT cygwin DOT com
Cc: cygwin AT cygwin DOT com
Subject: Re: How to install a custom permanent postinstall handler?
Content-Type: text/plain; charset="iso-8859-1"
In-Reply-To: <57027D59.5080509@redhat.com>
References: <57020525 DOT 90909 AT cygwin DOT com> <57027D59 DOT 5080509 AT redhat DOT com>
Date: Mon, 4 Apr 2016 17:37:35 +0200
Message-Id: <20160404173735.AC1CCA00.helmut.karlowski@ish.de>
MIME-Version: 1.0
Outgoingd: 0.4.0_m1
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u34Fc1oa004602

---------------------------------------------------
> On 04/04/2016 12:09 AM, Yaakov Selkowitz wrote:
> > On 2016-04-03 18:05, Andrey Repin wrote:
> >> Because, within my reach, Cygwin is the only system that not using
> >> DASH as
> >> /bin/sh. Though, I may try rolling some busybox…
> > 
> > There *is* a world outside of Debian/Ubuntu; Fedora, RHEL/CentOS, and
> > Arch Linux all use bash for /bin/sh.  However, a simple test in the form
> > of building GCC with dash as /bin/sh, while noticeably faster, showed
> > that Debian/Ubuntu have yet to fully upstream their work
> > ("gcc/genmultilib: 261: shift: can't shift that many").
> 
> And non-Linux systems use a completely different shell for /bin/sh
> (neither dash nor bash; BSD systems tend to use mksh).

OpenBSD uses the old pdksh with patches for /bin/sh and /bin/ksh.

-Helmut



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