On Sat, Mar 16, 2002 at 04:30:06PM +1100, Robert Collins wrote:
>I'd rather be _real_ simple about it. I.e. Offer a choice: reboot
>after the install or close app foo now. The user does one or the
>other, not a hybrid (close app foo after the install).
I think those are the only sane choices,
> -Original Message-
> From: Gary R. Van Sickle [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 16, 2002 4:14 PM
> PAIN! WINDOWS... DRIVERS! FILE... SYSTEM... AHA!!!
>
> Actually I was thinking this would be a perfect job for that
> snazzy new daemon coming down th
[snip]
> > But that doesn't really replace the current DLL. IOW the
> > changes are not
> > effective until one reboots. Personally I find this a crummy
> > way to do
> > things but perhaps that's all that can be done.
>
> I think crummy is a little harsh. And yes, other than shutting down all
>
> -Original Message-
> From: Christopher Faylor [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 16, 2002 2:29 PM
> >No its not - a rename operation on a memorymapped file fails. It's
> >under win16 *cough* win9x->Me that memorymapped files can be
> renamed or
> >deleted.
>
> It wo
On Sat, Mar 16, 2002 at 12:48:41PM +1100, Robert Collins wrote:
>
>
>> -Original Message-
>> From: Chris January [mailto:[EMAIL PROTECTED]]
>> Sent: Saturday, March 16, 2002 10:34 AM
>
>> > But that doesn't really replace the current DLL. IOW the
>> changes are
>> > not effective until
> -Original Message-
> From: Andrew DeFaria [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 16, 2002 10:06 AM
> > Same way as Windows installers work. Just schedule the DLL to be
> > moved in
> > after reboot.
>
> But that doesn't really replace the current DLL. IOW the
> change
> -Original Message-
> From: Chris January [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 16, 2002 10:34 AM
> > But that doesn't really replace the current DLL. IOW the
> changes are
> > not effective until one reboots. Personally I find this a
> crummy way to do things but perh
On Fri, Mar 15, 2002 at 11:34:07PM -, Chris January wrote:
>Under Win NT/2k/XP it is actually possible to replace a DLL file that's
>currently in use without rebooting. You rename the existing file to
>something else, then copy the new file in its place. Then add the old file
>to the MoveFileE
]
> Subject: Re: cygwin.com suggestions
>
> > >>>>2) Include in the FAQ (or somewhere) a section on "How to Safely
> Update the Cygwin dll". Probably just "shut down all cygwin apps,
> including
> daemons", but it would be useful to know for sure.
> &
> 2) Include in the FAQ (or somewhere) a section on "How to Safely
Update the Cygwin dll". Probably just "shut down all cygwin apps, including
daemons", but it would be useful to know for sure.
>
> >>>The next release of setup.exe automatically address's this and will
> >>>replace in-use
Larry Hall (RFK Partners, Inc) wrote:
> At 02:58 PM 3/15/2002, Andrew DeFaria wrote:
>
>>Robert Collins wrote:
>>
>>
2) Include in the FAQ (or somewhere) a section on "How to Safely Update the Cygwin
>dll". Probably just "shut down all cygwin apps, including daemons", but it would be
>usef
At 02:58 PM 3/15/2002, Andrew DeFaria wrote:
>Robert Collins wrote:
>
>>>2) Include in the FAQ (or somewhere) a section on "How to Safely Update the Cygwin
>dll". Probably just "shut down all cygwin apps, including daemons", but it would be
>useful to know for sure.
>>The next release of setup.e
Robert Collins wrote:
>>2) Include in the FAQ (or somewhere) a section on "How to
>>Safely Update the
>>Cygwin dll". Probably just "shut down all cygwin apps,
>>including daemons",
>>but it would be useful to know for sure.
>
> The next release of setup.exe automatically address's this and w
> -Original Message-
> From: [EMAIL PROTECTED]
>
> Here are a couple of suggestions for making the cygwin.com
> website more
> helpful.
Thanks for your suggestions, feedback on them in-line.
> 1) Include the current version number of setup.exe on the front page.
> Otherwise, there
14 matches
Mail list logo
