public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Re: New package: _autorebase.  Call rebaseall after installing new or updated DLLs
       [not found] <20120327153750.GM30721@calimero.vinschen.de>
@ 2012-03-28  9:49 ` Warren Young
  2012-03-28 12:16   ` Corinna Vinschen
  0 siblings, 1 reply; 2+ messages in thread
From: Warren Young @ 2012-03-28  9:49 UTC (permalink / raw)
  To: The Cygwin Mailing List

On 3/27/2012 9:37 AM, Corinna Vinschen wrote:
>
> Please also note that this package requires at least the new rebase
> version 4.1.0.  The changes in rebase 4.1.0 deal gracefully with DLLs
> which are in use while rebaseall runs.

Does this mean I can continue to leave the cron service running through 
a setup.exe upgrade as long as neither cygwin1.dll nor cyggcc_s-1.dll is 
being upgraded?  (Nor cron itself, obviously.)

I ask because the last time I ran rebaseall, it insisted I stop the cron 
service.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: New package: _autorebase.  Call rebaseall after installing new or updated DLLs
  2012-03-28  9:49 ` New package: _autorebase. Call rebaseall after installing new or updated DLLs Warren Young
@ 2012-03-28 12:16   ` Corinna Vinschen
  0 siblings, 0 replies; 2+ messages in thread
From: Corinna Vinschen @ 2012-03-28 12:16 UTC (permalink / raw)
  To: cygwin

On Mar 28 03:48, Warren Young wrote:
> On 3/27/2012 9:37 AM, Corinna Vinschen wrote:
> >
> >Please also note that this package requires at least the new rebase
> >version 4.1.0.  The changes in rebase 4.1.0 deal gracefully with DLLs
> >which are in use while rebaseall runs.
> 
> Does this mean I can continue to leave the cron service running
> through a setup.exe upgrade as long as neither cygwin1.dll nor
> cyggcc_s-1.dll is being upgraded?  (Nor cron itself, obviously.)

Yes, that should be possible.  You will find a list of DLLs which
couldn't be rebased in setup.log afterwards, but they are not
touched and rebase runs along.

Of course, this may have side effects.  Usually rebase packs the DLLs
side-by-side address-wise, so that they don't overlap and don't leave
holes in the memory layout.  In-use DLLs can hamper this effort so
there's a chance to leave holes.  And if, for some reason, two DLLs
are in use which overlap with each other, they will still overlap with
each other afterwards and can result in rebase problems subsequently.
Of course none of the rebased DLLs will overlap with the in-use DLLs.

Occassionally checking for overlaps with `rebase -si' doesn't hurt.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-03-28 12:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20120327153750.GM30721@calimero.vinschen.de>
2012-03-28  9:49 ` New package: _autorebase. Call rebaseall after installing new or updated DLLs Warren Young
2012-03-28 12:16   ` Corinna Vinschen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).