Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Thu, 28 Feb 2002 10:28:00 -0500 From: Jason Tishler Subject: Re: setup.exe rebase patch In-reply-to: <20020227025945.GA26911@redhat.com> To: cygwin-apps AT cygwin DOT com Mail-followup-to: cygwin-apps AT cygwin DOT com Message-id: <20020228152800.GB952@hp.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.3.24i References: <20020207134119 DOT GB1804 AT dothill DOT com> <027701c1bd28$c4666170$0200a8c0 AT lifelesswks> <20020225153441 DOT GA2544 AT hp DOT com> <018901c1be4f$6752fbb0$0200a8c0 AT lifelesswks> <20020226212652 DOT GC2288 AT hp DOT com> <3C7C491D DOT 7000302 AT ece DOT gatech DOT edu> <20020227025945 DOT GA26911 AT redhat DOT com> On Tue, Feb 26, 2002 at 09:59:45PM -0500, Christopher Faylor wrote: > However, I agree that rebasing shouldn't be the default behavior. In fact, > I wonder if I should make cygwin non-rebaseable. It would load faster if > I did that. OK. Then it would be best if you could make cygwin1.dll non-rebaseable. Otherwise, rebase will have to maintain a blacklist of DLLs too. I can easily leave a hole for cygwin1.dll (and other DLLs). However, the question then becomes how much space should be reserved? Right now 0x120000 is "needed" -- unfortunately, in the future, more may be needed. What happens then? Adding rebase functionality has uncovered more issues than I initially imagined. Assistance determining the essential requirements would be greatly appreciated. Thanks, Jason