On Apr 20 11:12, Bertalan Fodor wrote: > Problem with: > ln -s > > I remove > /bin/etex > > Create link: > ln -s /bin/pdfetex.exe /bin/etex > > A link is not created but a copy of /bin/etex.exe > > $ ls -al /bin/etex* > -rwxr-x---+ 1 fodorb Felhaszn?l?k 280064 Mar 10 15:21 /bin/etex.exe > > $ ln -s /bin/pdfetex.exe /bin/etex > $ ls -al /bin/etex* > -rwxr-x---+ 1 fodorb Felhaszn?l?k 280064 Mar 10 15:21 /bin/etex > -rwxr-x---+ 1 fodorb Felhaszn?l?k 280064 Mar 10 15:21 /bin/etex.exe > > If I remove /bin/etex.exe, the link is created successfully.
The link has been created correctly already the first time you called ln. The problem is that ls doesn't evaluate the information correctly because the underlying path handling finds the "tcsh.exe" file before it finds the "tcsh.lnk" file. While this is a problem which could be "fixed" in some way in Cygwin, I'm nevertheless wondering how you want the ambiguity to be solved. If you type "etex" on the command line, do you want etex -> pdfetex.exe to be started or etex.exe? Regardless how that's solved in Cygwin, it will work contrary to the expectations in 50% of the cases. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/
