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 Date: Tue, 9 Sep 2003 15:14:23 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: symlink extension shown using 1.5.3 Message-ID: <20030909131422.GS1859@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <14180.1063101920@www26.gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <14180.1063101920@www26.gmx.net> User-Agent: Mutt/1.4.1i On Tue, Sep 09, 2003 at 12:05:20PM +0200, stmoebius@gmx.de wrote: > Since I updated to cygwin 1.5.3 and bash 2.0.5b13, symlinks *on* network > drives are shown by ls including the '.lnk'. They are properly recognized as > symlinks and it is even possible to, e.g., change the directory using only the > link name (without '.lnk'). The reason is probably the missing R/O bit on the network drive. Can you check the properties dialog of one of these files when accessing them remote? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer 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/