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
Message-ID: <8F23E55D511AD5119A6800D0B76FDDE1CA3018@cpex3.channelpoint.com>
From: Troy Noble <troy DOT noble AT channelpoint DOT com>
To: "'Gary R Van Sickle'" <tiberius AT braemarinc DOT com>,
        "Cygwin Mailing List (E-mail)" <cygwin AT sourceware DOT cygnus DOT com>
Subject: RE: tar 'mini'-bug
Date: Wed, 8 Aug 2001 13:27:11 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Scanned-By: MIMEDefang 1.0 (http://www.roaringpenguin.com/mimedefang/)

Isn't setup.exe able to upgrade cygwin1.dll in place?
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 ;->

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

But if setup.exe will work, use that instead.

Troy

-----Original Message-----
From: Gary R Van Sickle [mailto:tiberius AT braemarinc DOT com]
Sent: Wednesday, August 08, 2001 1:01 PM
To: Cygwin Mailing List (E-mail)
Subject: tar 'mini'-bug


For a long time tar has been behaving strangely, and I'm just reporting it
since I can't seem to find anybody else that has.  If I 'tar -xjf' a
snapshot overtop of the current cygwin installation on Why2K, I get this,
what I assume is the expected result since cygwin1.dll is being used by tar
and bash:

$ tar -xjf cygwin-inst-20010807.tar.bz2
tar: usr/bin/cygwin1.dll: Cannot open: File exists
tar: Error exit delayed from previous errors

Now when I do the exact same thing on the universally-hated Windows 'ME',
tar simply hangs and must be killed by a CTRL-C.  '--exclude=cygwin1.dll' of
course makes it work fine.

Just wanted to make this a known issue.  Perhaps someday after I've purged
all memory of the "\n / \r\n / \r / CTRL-Z / no CTRL-Z" fiasco from the
collective memory I'll take a look inside and see what's causing this
difference.

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/

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