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
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3C580A57.1B13628C@lapo.it>
Date: Wed, 30 Jan 2002 15:59:47 +0100
From: Lapo Luchini <lapo AT lapo DOT it>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: it,en,fr,es,ja
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: soft links and windows prompt
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

As I like to use cygwintools also from windows prompt, I added
f:\cygwin\bin to the path. No problem here.

One probles is when I try to gunzip... gzip.exe is a "normal" exe, while
gunzip.exe (while showing up as a symlink from bash) is not a real exe
but a text file containing "!<symlink>gzip.exe" (though symlink creates
with "ln -s" create a linkname.lnk, as somewhat supported by windows
itself (not in the prompt AFAIK)).. the problem is that windows executes
gunzip.exe as it was a real exe and, obviously, dumps.
Same problem with python.exe -> python2.2.exe and so on.

I found useful to delete the symlinked gunzip.exe and use instead a hard
link (created with "ln")... as of this morning I didn't know NTFS
supported that and I was pretty impressed when "ln" worked perfectly ;)

Regarding the "dump problem"... is that ".exe containing !<symlink>" an
"old" method to create symlinks?

--
Lapo 'Raist' Luchini
lapo AT lapo DOT it (PGP & X.509 keys available)
http://www.lapo.it (ICQ UIN: 529796)



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