X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-type :content-transfer-encoding; q=dns; s=default; b=gA7wfxQOAVOeFPAx QcPaahqXB7nW6jXSll6Ayki+WnZu2B2Y2mxv06lKejmDNPosGzCWyFA/YOhxdxZA Fhd/DID++qpR/UrRPTZvcssQOW+2xid/rU5MJ4sW8Umam/fhHbjXm1u+l1oeCr3l rUQA0dRbqOZxPFR4k04aP9CkWX0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=default; bh=18M8q2NrvLfh6yK2WTbC97 dFX1s=; b=cCh4qOeKOtrc1hQeqCDgaE5SmO9dcU0UJnSYM0llk75Qv65h+GRWFW XXUNWYqrqKEsdsIX0EQzws2W81L9UkPzw8IkMd7VDjXcytTtSp2EAGpDFTcjcttc MXHbLMXoXQ5DQeiAsG/0kh36yuFOyweu/oUkaNCYcfL6uWD/0Z3f4= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: smtpback.ht-systems.ru Date: Mon, 7 Apr 2014 22:04:27 +0400 From: Andrey Repin Reply-To: cygwin AT cygwin DOT com Message-ID: <1675705369.20140407220427@yandex.ru> To: Corinna Vinschen Subject: Re: Request for Junctions be treated consistently In-Reply-To: <20140407092342.GF2061@calimero.vinschen.de> References: <5336C0DF DOT 5080102 AT tlinx DOT org> <5336C23B DOT 2070309 AT tlinx DOT org> <20140331102745 DOT GD23383 AT calimero DOT vinschen DOT de> <533AEBD6 DOT 3040209 AT tlinx DOT org> <20140402084026 DOT GM2508 AT calimero DOT vinschen DOT de> <533FE56D DOT 5010809 AT tlinx DOT org> <20140407092342 DOT GF2061 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Greetings, Corinna Vinschen! >> I don't think your original concern is as big a problem as you >> think, as is indicated by the above setup on linux. >> >> I.e. is there some other reason to not treat "linkd" mounts >> the same as "mountvol" mounts -- in a manner equivalent to linux's >> 'bind' mounts? >> >> I.e. I don't see that that linkd which creates a junction-mount >> point, should be treated as a symlink. It would provide valuable >> benefit in cygwin terms in being able to setup directories at >> multiple place like 'bind' does on linux, and be resistant to being >> overwritten like symlinks. > Look, directory reparse points are, by and large, symlinks to another, > real directory entry. The directory has a primary path, which is its > own path under which it has been created, and the reparse point is just > a pointer to this directory. If that's not a symlink, what is? Uhm, there's two ways to look at it. You may call it a "symlink", but in fact, Linux equivalent of a reparse point is a mount --bind, or, perhaps, a block-type device mounted at specific directory. It's a [literal] filesystem junction (in common meaning of "junction"), while symlink is more like conventional language construct. I.e., you can make a reparse point to local resource, that was not assigned a drive letter. Enough that it's a local filesystem, and you know it's UUID. But you can't make a reparse point to a network share, for example, even if that share is mapped to a drive letter. But you can make a [native] symlink to it. -- WBR, Andrey Repin (anrdaemon AT yandex DOT ru) 07.04.2014, <21:55> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple