Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <42D671F0.F1C1CDB1@dessent.net>
Date: Thu, 14 Jul 2005 07:08:48 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: rebaseall (was Re: Perl Win32::Shortcut screws up fork)
References: <SERRANOxBowfKDNmuQ20000053b AT SERRANO DOT CAM DOT ARTIMI DOT COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Report: -5.9/5.0 ---- Start SpamAssassin results  	* -3.3 ALL_TRUSTED Did not pass through any untrusted hosts 	* -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% 	*      [score: 0.0000] 	*  0.0 AWL AWL: From: address is in the auto white-list 	---- End SpamAssassin results
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Dave Korn wrote:

>   Out of curiosity, why isn't "exec /bin/sh.exe rebaseall" the solution to
> this problem?

It would, presuming you meant /bin/ash.exe and the user hadn't removed
the ash package.  It would help if the rebaseall shebang was #!/bin/ash,
then you could type "exec rebaseall".

I suppose it's a good idea for a temporary work around, but it's
essentially the same thing as telling the user to open a regular windows
command prompt and run "ash rebaseall".  I guess we already require them
to shut down all cygwin processes and start a non-rxvt/xterm prompt, so
having them type more than a simple 'rebaseall' doesn't really add too
much burden.

I still think that getting --enable-auto-image-base working is the best
long-term solution.

Brian

--
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/