From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24506 invoked by alias); 9 Mar 2017 15:48:49 -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 24368 invoked by uid 89); 9 Mar 2017 15:48:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=BAYES_00,GIT_PATCH_2,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*i:sk:1599023, H*f:sk:1599023, H*MI:sk:1599023, Hx-languages-length:764 X-HELO: Ishtar.sc.tlinx.org Received: from ishtar.tlinx.org (HELO Ishtar.sc.tlinx.org) (173.164.175.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 09 Mar 2017 15:48:46 +0000 Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id v29Fmhoe028306 for ; Thu, 9 Mar 2017 07:48:45 -0800 Message-ID: <58C1795B.5010809@tlinx.org> Date: Thu, 09 Mar 2017 15:48:00 -0000 From: L A Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Treating Junctions consistently, as "normal dirs" as w/linux "bind"-type mount 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> In-Reply-To: <1599023500.20170309163724@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00116.txt.bz2 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 would you want to treat them? -- 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