From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28987 invoked by alias); 10 Mar 2017 13:20:48 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 28919 invoked by uid 89); 10 Mar 2017 13:20:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,GIT_PATCH_2,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=UD:ru, letter, HX-Priority:Normal X-HELO: forward2j.cmail.yandex.net Received: from forward2j.cmail.yandex.net (HELO forward2j.cmail.yandex.net) (5.255.227.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 10 Mar 2017 13:20:41 +0000 Received: from smtp3o.mail.yandex.net (smtp3o.mail.yandex.net [37.140.190.28]) by forward2j.cmail.yandex.net (Yandex) with ESMTP id 70F6E20CB0; Fri, 10 Mar 2017 16:20:39 +0300 (MSK) Received: from smtp3o.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp3o.mail.yandex.net (Yandex) with ESMTP id C9F732940D9A; Fri, 10 Mar 2017 16:20:37 +0300 (MSK) Received: by smtp3o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id pcWfXjCtvy-KaU8JPrW; Fri, 10 Mar 2017 16:20:36 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) Authentication-Results: smtp3o.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0 Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Fri, 10 Mar 2017 13:17:23 -0000 Date: Fri, 10 Mar 2017 13:20:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <212519238.20170310161723@yandex.ru> To: L A Walsh , cygwin@cygwin.com Subject: Re: Treating Junctions consistently, as "normal dirs" as w/linux "bind"-type mount In-Reply-To: <58C1795B.5010809@tlinx.org> References: <58A4741E.5020408@gmail.com> <20170216092611.GE3889@calimero.vinschen.de> <58B0AA58.30504@tlinx.org> <20170228214321.GB13542@calimero.vinschen.de> <58C0D744.2030005@tlinx.org> <1599023500.20170309163724@yandex.ru> <58C1795B.5010809@tlinx.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00130.txt.bz2 Greetings, L A Walsh! > Andrey Repin wrote: >> I would argue against all junctions being treated blindly. >> The difference with bind mounts in Linux is that in Linux >> you don't have the >> information available within the filesystem itself, and have >> no other option, >> than to treat them as regular directories. >> Only direct volume junctions cause an issue, and this is what >> should be fixed, >> if possible, not sidetracked with questionable workarounds. > ---- > Could you describe the benefits of your proposed solution? > You do know that MS originally called junctions "mountpoints", > right? So why would cygwin treating them as such be a "questionable > workaround"? How they are called, and how they behave is a two different questions. > How would you want to treat them? Easy way: As symlinks, just like now, unless it's a volume mount point that can't be normalized to a disk letter. Preferred way: Fix volume mounts accessibility \\?\{UUID} -> /dev/disk/by-uuid/UUID -- With best regards, Andrey Repin Friday, March 10, 2017 16:10:57 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