Message-ID: <458F81CC.3090500@tlinx.org>
Date: Sun, 24 Dec 2006 23:46:20 -0800
From: Linda Walsh <cygwin@tlinx.org>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Updated cygwin dlls don't have the .dll extension; instead have   .dll.new
References: <458EE598.3010404@aim.com> <458F31B1.6050804@byu.net>
In-Reply-To: <458F31B1.6050804@byu.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Eric Blake wrote:
> According to Charli Li on 12/24/2006 1:39 PM:
>   
>>  Fishy enough, the new dlls had a filename extension of .dll.new
>>     
> Which means Windows is scheduled to rename it automatically at the next
> reboot, since it was in use at the time you ran setup.exe.  Didn't you
> read the message box that setup told you to reboot?
>   
>> Bottom line: Is this a problem with setup.exe?  CCing to cygwin-apps as
>> well.
>>     
> No, this is not a setup bug, but a Windows limitation
---
    It has a name extension of .new because that's what cygwin sets it to.
Cygwin has a limitation that doesn't need to exist. 

Cygwin could rename the old file to file.dll.old, (or if it isn't 
cross-deviced linked,
to "/tmp/file.dll.todelete.001") and move the new file into "file.dll".  
It's an established
behavior of NT. 

Perl had same problem when installing new perl libraries under Windows.  
They moved
to the NT supported method of renaming the old and putting in the new.  
Then you still
setup the file delete after reboot -- but meanwhile, users can use the 
new library,
and programs that have the existing file open continue to operate "fine" 
until they
exit -- then it's the old files that get left around until the next reboot.

-l


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