Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Wed, 3 Aug 2005 16:35:43 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin and NTFS Junction Points
Message-ID:	<20050803143543.GF14783@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<dcqdg9$2hn$1 AT sea DOT gmane DOT org>
Mime-Version:	1.0
In-Reply-To:	<dcqdg9$2hn$1@sea.gmane.org>
User-Agent:	Mutt/1.4.2i

On Aug  3 14:32, Frank-Michael Moser wrote:
> Since I have discovered NTFS Junction Points (NTFS 5.0+) I'm using them
> frequently to symbolically link directories in a POSIX conformous way:
> The junction points (JP) are transparent to *any* program using the
> filesystem.
> 
> Unfortunately there are bizarre issues related to manipulating JPs from
> the explorer or with DOS commandline tools:
> 
> http://encyclopedia.thefreedictionary.com/NTFS%20Junction%20point
> http://shell-shocked.org/article.php?id=284
> 
> But there are tools which help to avoid these bizarre effects. E.g.
> http://www.elsdoerfer.info/ntfslink/ is an explorer extensions which
> hooks into Windows Explorer, providing extended functionality for
> creating and using JPs on NTFS file systems.
> 
> Now has anybody thought about respecting JPs under Cygwin? Respecting
> JPs at least would mean:
> 
> a) recursively copying JPs (or their parent folders) should not
> recursively copy the content of a JP but copy the JP itself (reproducing
> it at the new location, if possible)
> 
> b) recursively removing JPs (or their parent folders) should not
> recursively remove the content of a JP but remove the JP itself (leaving
> the content of its target folder untouched)
> 
> c) moving JPs (or their parent folders) should not recursively move the
> content of a JP but move the JP itself (leaving the content of its
> target folder untouched)
> 
> Wouldn't this be a valid improvement to Cygwin, at least as an option?
> What is your opinion?

Well... doesn't find -xdev do the job sufficiently already?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT 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/

- Raw text -