X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sun, 16 Mar 2008 16:26:49 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: ash/bash postinstall dance [Was: Cygwin doesn't install on Windows Server 2008 (x64).] Message-ID: <20080316152649.GC19345@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <47DB6508.50E4B9C9@dessent.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47DB6508.50E4B9C9@dessent.net> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mar 14 22:56, Brian Dessent wrote: > Krzysztof Ostrowski wrote: > > > What is the purpose of "00ash.sh", and what kind of system calls does it > > attempt at making? Surely, it must be something very unusual because I've got > > The strange thing about this is that 00ash should be totally superfluous > on a new system. And syscalls? It's a shell script, it's just invoking > programs, it doesn't really know waht a syscall is. > [SNAP] I can simply remove the 00ash.sh script. From my point of view, we should define bash as sh in a rather notorious way. There's no strong reason to define ksh or zsh as sh. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/