Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) From: "Andrej Borsenkow" To: "Cygwin Mailing List" Subject: RE: [ANNOUNCEMENT]: Important change to symbolic link functionali ty Date: Fri, 23 Feb 2001 10:52:31 +0300 Message-ID: <000501c09d6d$932ab6a0$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20010222184404.S908@cygbert.vinschen.de> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 > > The shortcut contains a DOS path and a POSIX path. The POSIX path is > used by Cygwin or U/WIN. The DOS path is used by native Windows tools, > obviously. > That is, when I open shortcut properties in Explorer I see DOS path? Then there is a possibility that user changes shortcut there and DOS/Cygwin paths differ. One way to store paths checksums in .lnk; but it is not clear what to do in this case - you cannot recreate possibly relative Unix path from changed DOS one. Probably, in this case the right thing is to invalidate Unix path in shortcut alltogether. If symlinks are implemeted as shortcuts, it may turn out to be quite a common problem. -andrej -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple