X-Spam-Check-By: sourceware.org
Date: Wed, 15 Mar 2006 11:14:03 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: RE: Problems with setup.exe updates when cygwin is running
In-Reply-To: <007b01c64843$1d466840$a501a8c0@CAM.ARTIMI.COM>
Message-ID: <Pine.GSO.4.63.0603151108560.27892@access1.cims.nyu.edu>
References: <007b01c64843$1d466840$a501a8c0 AT CAM DOT ARTIMI DOT COM>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Wed, 15 Mar 2006, Dave Korn wrote:

> On 15 March 2006 15:08, Andrew MacCormack wrote:
>
> > I've just had a bunch of problems with cygwin, including but not limited
> > to those experienced here:
> > http://www.cygwin.com/ml/cygwin/2006-01/msg00798.html
> > http://www.cygwin.com/ml/cygwin/2006-01/msg00798.html
> >
> > As it turns out in the end, these have been down to running setup.exe
> > with cygwin running and getting the mesage about needing to reboot.
> > However, even after reboot the system has been broken: inodes listed as
> > changed, cp saying that files were changed during copy, etc. This all
> > seems to be down to the setup.exe run. After reverting everything to
> > previous, the problem has gone away entirely. I suggest that setup.exe
> > needs robusting, at the very least giving a strong warning on update
> > BEFORE changing things if the files are in use.
>
>   Basically I don't think it should let you update if things are still
> in use. Even though files can be replace-on-rebooted, that doesn't help
> the fact that the postinstall scripts might not have run.

It could tell you that the files are in use, and offer to close
applications and retry.  FWIW, the patch for this has already been
submitted, but has not yet been applied.  See the discussion at
<http://cygwin.com/ml/cygwin-apps/2006-02/msg00099.html>.

> > A general message to close running programs before installing is used as
> > a cop-out by lots of other programs and is usually overkill, and thus
> > ignored. So it needs to be clear and specific, if it is to be effective.
>
>   I'm in agreement with you there.  We're working on a patch for it at
> the moment.  I think it should either refuse to go any further, or offer
> to kill everything for you.

Or let you retry, in case you forgot to close something.

> > Maybe I've been spoiled by the support I've received on other free
> > forums and from commercial companies who don't tell their customers to
> > push off.
>
>   I promise you, if you pay me money I won't tell you to push off either!

We offer something commercial companies rarely do -- an opportunity to
influence the future direction of the project by writing the code
yourself. :-)  That is not to say that you must do that, but
<http://cygwin.com/acronyms/#SHTDI>.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

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