Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Sat, 9 Jul 2005 10:54:39 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Eric Blake cc: fergus AT bonhard DOT uklinux DOT net, cygwin AT cygwin DOT com Subject: Re: Unwanted .exe appended to symlinks In-Reply-To: <42CFD190.2060109@byu.net> Message-ID: References: <1120880636 DOT 6400 DOT 7 DOT camel AT localhost DOT localdomain> <42CFD190 DOT 2060109 AT byu DOT net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 9 Jul 2005, Eric Blake wrote: > Technically, symlink creation should not need to check > the source's existence (after all, that's why creating dangling symlinks > is possible), but cygwin has to do it to make .exe magic more consistent. Eric, I appreciate the effort you spend to get this right, and hate to ask for extras (especially if those are non-standard), but would it be possible to add a Cygwin-specific option[*] to ln that disables this? The reason is that I frequently create symlinks to files/directories on network shares, and those shares aren't always available. When they aren't, any access to them locks up the shell until the SMB request times out (which can take a while and isn't interruptible). Having ln always check the target of the symlink will make "ln -s" nigh unusable. Igor [*] I'd suggest --disable-exe-magic (no need to expend a short option) -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/