1.7.7 ln .exe magic
test case--- From bash, in an empty directory: $ ln /bin/ls t $ ls t.exe Why does the resulting hard link have a '.exe' suffix on it? I thought that cygwin .exe magic was only appending when listing a file? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.7 ln .exe magic
On 09/15/2010 11:03 AM, Rolf Campbell wrote: test case--- From bash, in an empty directory: $ ln /bin/ls t $ ls t.exe Why does the resulting hard link have a '.exe' suffix on it? I thought that cygwin .exe magic was only appending when listing a file? If the original file ends in .exe, then cp tries hard to make the target also end in .exe. The .exe magic for invoking 'ls' (instead of ls.exe) will therefore let you also invoke 't' (instead of t.exe), while still letting you run .\t from cmd (where the lack of a .exe suffix would break that attempt). So the .exe magic is more than just when listing a file. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.7 ln .exe magic
Greetings, Rolf Campbell! test case--- From bash, in an empty directory: $ ln /bin/ls t $ ls t.exe Why does the resulting hard link have a '.exe' suffix on it? I thought that cygwin .exe magic was only appending when listing a file? It's quite expected. If source has .exe, the target will, too, for transparent compatibility. -- WBR, Andrey Repin (anrdae...@freemail.ru) 15.09.2010, 21:35 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
