Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: "Gary R Van Sickle" <tiberius AT braemarinc DOT com>
To: "'Cygwin Mailing List (E-mail)'" <cygwin AT sourceware DOT cygnus DOT com>
Subject: RE: tar 'mini'-bug
Date: Wed, 8 Aug 2001 16:40:28 -0500
Message-ID: <001501c12052$be449fa0$2101a8c0@nomad>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006
Importance: Normal
In-Reply-To: <8F23E55D511AD5119A6800D0B76FDDE1CA3018@cpex3.channelpoint.com>

> Isn't setup.exe able to upgrade cygwin1.dll in place?

Not to the snapshots according to the FAQ.  Hang on, let me try it though...
nope.

> I thought it could.  If so, that's by far your best bet.
>
> This is a Windows behavioral problem, not a cygwin issue.
>
> On the NT family of OS's, you can't overwrite a DLL that's
> currently in use.  It's locked.  That's why you get that
> message.
>
> On Windows ME (a.k.a. DOS 9 or is it DOS 10?  I forget.) there
> are no such strict file locking semantics, so in my understanding
> the behavior is somewhat undefined if you try to overwrite a DLL
> on a FAT32 partition when it's currently in use.  I've never tried
> it.  But I would say it's not a wise thing to do ;->
>

Mmmm, I think you're wrong on that.  I believe ME, crappy as it is, gets
this one thing right and behaves the same as Why2K in that respect, in that
you can't write to an executable file that's in use by the OS.  I'm not at a
ME system right now though so I can't verify that.

> But you can take advantage of the fact that Win32 first
> attempts to load a DLL from the directory where the .exe
> resides before scanning the PATH.  Copy tar.exe and
> cygwin1.dll to some other location, maybe c:\temp.  Then
> run
>
> bash$ /cygwin/c/temp/tar xvf <filename>
>
> to get around this problem.  Then go delete your temporary
> cygwin1.dll since you're not supposed to let multiples of
> them reside on your system at the same time ;->
>

Well right, I can (and do) easily get around it, but my point is that I
don't think tar should be hanging on ME if it's not able to write to a file.

Gary R. Van Sickle
Braemar Inc.
11481 Rupp Dr.
Burnsville, MN 55337


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