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:29:36 -0400 From: Jason Tishler To: cygwin AT cygwin DOT com Subject: Re: Invoking ash for rebaseall Message-ID: <20050718112936.GA796@tishler.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <003b01c58b08$9c1b4800$6400000a AT RossLap> <20050717205915 DOT GA2656 AT tishler DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Igor, On Mon, Jul 18, 2005 at 01:57:52AM -0400, Igor Pechtchanski wrote: > On Sun, 17 Jul 2005, Jason Tishler wrote: > > On Sun, Jul 17, 2005 at 02:48:39PM -0500, Ross Boulet wrote: > > > Granted, I could go in to windoze and add the cygwin directories > > > to my system path, or manually source /etc/profile at the ash > > > prompt. But is there a flag to tell ash to act as a login shell > > > and execute /etc/profile? > > > > Just use the following (from ash): > > > > $ PATH=/bin rebaseall > > 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? It would be easier to just add "PATH=/bin" near the beginning of the rebaseall script than to use full paths for every command invocation. Unfortunately, this would not solve the problem of finding rebaseall itself. Anyway, maybe the best approach is to add the aforementioned PATH setting to rebaseall and instruct the user to execute rebaseall as follows: $ /bin/rebaseall Any other suggestions? 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/