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 Message-ID: <42F113B6.843BA07D@dessent.net> Date: Wed, 03 Aug 2005 11:57:58 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Cygwin and NTFS Junction Points References: <080320051737.1393.42F100EC00014F6E0000057122007358340A050E040D0C079D0A@comcast.net> <42F11228.2030305@air2web.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Report: -5.4/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.5 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Richard Campbell wrote: > > To some degree, Junction Points are more like directory HARD links, > > rather than symlinks. > > What degree is this? > > Everything I can see seems to say junction points function as symlinks > for directories, with retargeting, dangling, and fixing options. > > I admit the documentation I have been looking at is sketchy - do you > have some better info? You can't use a junction point to make a relative link, as you can with symbolic links. That makes them significantly less useful. Brian -- 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/