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 To: cygwin AT cygwin DOT com From: Frank-Michael Moser Subject: Re: Cygwin and NTFS Junction Points Date: Wed, 03 Aug 2005 18:54:04 +0200 Lines: 57 Message-ID: References: <20050803143543 DOT GF14783 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) In-Reply-To: <20050803143543.GF14783@calimero.vinschen.de> X-IsSubscribed: yes Unfortunately "find -xdev" does not work because junction points also can point to target folders on the same filesystem. Also I meant that using fileutils like cp, mv, and rm should transparently respect junction points and handle them in like symlinks under Linux as I described it in my post. At the moment I must pay highest attention *not* to use these tools recursively on junction points or their parents to avoid bizarre behaviour like unexpected vanishing of the targeted files. Frank-Michael Corinna Vinschen wrote: > 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 > -- 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/