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: Thu, 27 Nov 2003 18:37:39 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: a couple of problems/items with managed mounts Message-ID: <20031127233739.GA15656@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20031127183649 DOT GA3832 AT ingber DOT com> <20031127225945 DOT GC29208 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031127225945.GC29208@redhat.com> User-Agent: Mutt/1.4.1i Note-from-DJ: This may be spam On Thu, Nov 27, 2003 at 05:59:45PM -0500, Christopher Faylor wrote: >On Thu, Nov 27, 2003 at 10:36:49AM -0800, Lester Ingber wrote: >>I don't understand when and why ".lnk" is attached as a suffix when I >>create soft links. > >Cygwin has a random "mean" mode. It is very effective in producing >unpredictable results with the .lnk extension. I'm generating a snapshot now which fixes this problem, which can be summarized as "A .lnk extension shows up in some cases for symbolic links in directory listings if the filename contains characters which cygwin considers to be 'special', like upper case characters, colons, etc." Check the cygwin.com web page and click on the "Snapshots" link on the left sidebar to find out about snapshots. Don't bother downloading a snapshot unless it displays today's date or newer. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam AT sourceware DOT org and be permanently blocked from mailing lists at sources.redhat.com -- 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/