Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Wed, 18 Sep 2002 14:18:31 +0200 (CEST)
From: Pavel Tsekov <ptsekov AT gmx DOT net>
X-X-Sender: ptsekov AT moria
To: John Carlyle- Clarke <john DOT cc AT europlacer DOT co DOT uk>
cc: "Cygwin List (E-mail)" <cygwin AT cygwin DOT com>
Subject: RE: Setup 2.249.2.5 Hangs during "Install from Local Directory"
In-Reply-To: <A25942DDD06FC94E8AF6AF0B4CD6D60F0A75E7@prime.europlacer.net>
Message-ID: <Pine.LNX.4.44.0209181411530.14485-100000@moria>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 18 Sep 2002, John Carlyle- Clarke wrote:

Please, ask about one problem at a time.  Is setup which is 
causing problems for you or some of the Cygwin packages ?

I was under the impression that you're having troubles installing Cygwin 
due to a setup.exe misbehaving. Now I see that you've succeeded in 
installing Cygwin. I am really puzzled right now.

> > > This problem seems to occur when the setup program tries to 
> > > access a file for writing for which it does not have permission.
> > 
> > Well, is there a chance you know also the name of the file. And is it 
> > really a single file or a directory ? 
> 
> It really doesn't matter which file - the problem occurred with any file that setup wanted to write for which it did not have write permissions.  If you want an example, I remember it occurring with /usr/lib/ldscripts/i386pe.x but it could have been any other file.
> 
> I think there may be a more general problem here.  I messed up all my file permissions, which is how this problem came to light, and I am slowly putting them right.
> 
> However, I am getting exactly the same problem with crontab.  It doesn't have permission to write in /var/cron/tabs, and when you crontab -e and finish editing, it hangs up, using 98% CPU.
> 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/