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 X-Originating-IP: [66.188.107.59] X-Originating-Email: [pbrockill@hotmail.com] From: "P. Brockill" To: cygwin@cygwin.com Subject: RE: Why do symlinks need to be system files Date: Thu, 10 Jul 2003 22:28:38 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Message-ID: X-OriginalArrivalTime: 10 Jul 2003 22:28:38.0148 (UTC) FILETIME=[9BA14440:01C34732] Hi, >Sure. Use new-style symlinks (i.e., shortcuts). They only need to be >read-only, IIRC. Make sure your CYGWIN variable doesn't contain >"nowinsymlinks", though. > Igor Sounds right enough, but: don't the new-style symlinks always contain the full path to the file (e.g. e:\some_dir\some_file.ext)? (Although I see from the text of the .lnk file that they also keep a cygwin path in the comment section as well) So say I want to make a link on a CD to another file on that CD called e:\some_dir\some_file.ext . Won't this fail when I try to see the link on a computer where the CD drive is d: ? Thanks for the help, Cheers. _________________________________________________________________ MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl -- 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/