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 Message-ID: <42F11923.4040700@opnet.com> Date: Wed, 03 Aug 2005 21:21:07 +0200 From: Stein Somers User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin and NTFS Junction Points References: <080320051737 DOT 1393 DOT 42F100EC00014F6E0000057122007358340A050E040D0C079D0A AT comcast DOT net> <42F11228 DOT 2030305 AT air2web DOT com> <42F113B6 DOT 843BA07D AT dessent DOT net> In-Reply-To: <42F113B6.843BA07D@dessent.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Brian Dessent wrote: > You can't use a junction point to make a relative link, as you can with > symbolic links. That makes them significantly less useful. But still a giant leap from setting up drive letters with subst, which used to be the only Windows way I know to introduce a layer of indirection in file naming. As a user of junction points, outside of cygwin, I would label them symlinks to directories only that you have to remove with rmdir. Stein -- 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/