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 [EMAIL PROTECTED] (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/
