Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <00de01c32b24$f9b806b0$710d86d9@ellixia> From: "Elfyn McBratney" To: "cygwin" , "S. L." References: <16740 DOT 1054791181 AT www68 DOT gmx DOT net> Subject: Re: setup problem: only ash comes as /bin/sh Date: Thu, 5 Jun 2003 06:40:29 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 > I reinstalled my w9x box and cygwin also. > As the subject mentions, this is already annoying: every time I reinstall > cygwin, I must remember to set a /bin/sh, and re-run all /etc/postinstall > scripts, since the only shell I install is bash, and the only /bin/sh installed by > setup is ash. > Could this be fixed somehow? How exactly? Ash is a part of the 'Base' category, a minimal Cygwin installation. This means that postinstall scripts et al expect a 'Base' install ie., they expect ash to be installed. Adding a symlink `bash -> sh' to the bash packages is an option, but c'mon what's ~40K between Cygwin'ers? :-) Elfyn -- 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/