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 Date: Mon, 18 Jul 2005 07:42:05 -0400 From: Jason Tishler To: cygwin AT cygwin DOT com Subject: Re: Invoking ash for rebaseall Message-ID: <20050718114205.GB796@tishler.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <003b01c58b08$9c1b4800$6400000a AT RossLap> <20050717205915 DOT GA2656 AT tishler DOT net> <42DB4708 DOT 922E20EB AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42DB4708.922E20EB@dessent.net> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes On Sun, Jul 17, 2005 at 11:07:04PM -0700, Brian Dessent wrote: > Igor Pechtchanski wrote: > > Umm, why should rebaseall require a PATH setting at all? Wouldn't > > it be easier to specify full paths for every command instead of > > telling users to set their PATH? > > Well, if the user does not have /usr/bin in their Windows path > (instead relying on /etc/profile to add it) and they try to run "ash > rebaseall" from a command prompt, they will get an error about not > finding cygwin1.dll unless /usr/bin is the CWD. Actually, "ash rebaseall" will not work even if the user's PATH is set correctly. Unlike bash, ash does not seem to search the PATH to find a script to execute: $ ash foo.sh foo.sh: Can't open foo.sh: No such file or directory But, the following work: $ ash /home/jt/bin/foo.sh foo $ ash -c foo.sh foo Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- 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/