Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: Re: Unwanted .exe appended to symlinks From: fergus Reply-To: fergus@bonhard.uklinux.net To: cygwin@cygwin.com Cc: fergus@bonhard.uklinux.net Content-Type: text/plain Date: Sat, 09 Jul 2005 04:57:08 +0100 Message-Id: <1120881428.6584.8.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit The reason mentioned in the previous posting for re-creating symlinks is that periodically (after several updates) I run through all 3000 of them re-creating them; that way I can be sure they are all Windows +R *.lnk files rather than Windows +S files, which can't be guaranteed to copy properly to other media. So, I wonder, has an unwanted trailing .exe been incorporated in other contexts than that described in the previous post? Not that I can see. No problems with (say) ln -s oldname extraname where oldname is a textfile. Also, in other cases where oldname really is an executable, extraname does not seem to have the trailing .exe. There must be something special about doing this with a drivename. Can any expert confirm whether I ought to look elsewhere for this strange appendix? I admit it's my fault for meddling but it's not that daft an activity to have pursued, and certainly ln -s /cygdrive/c /c must be a fairly common solution to an annoying problem (that of having to write a lot). Fergus -- 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/