From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24735 invoked by alias); 6 Sep 2016 22:07:42 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 24723 invoked by uid 89); 6 Sep 2016 22:07:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*Ad:U*mark, dig, life X-HELO: m0.truegem.net Received: from m0.truegem.net (HELO m0.truegem.net) (69.55.228.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 06 Sep 2016 22:07:40 +0000 Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id u86M7dDw019098 for ; Tue, 6 Sep 2016 15:07:39 -0700 (PDT) (envelope-from mark@maxrnd.com) Received: from 76-217-5-154.lightspeed.irvnca.sbcglobal.net(76.217.5.154), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpdTnfz6f; Tue Sep 6 15:07:31 2016 Subject: Re: [ITP] FUSE 2.8 To: cygwin-apps@cygwin.com References: <579A4102.9040406@maxrnd.com> <20160728200435.GG26311@calimero.vinschen.de> <20160729085141.GK26311@calimero.vinschen.de> <20160817091433.zksukafls6mkk52u@calimero.vinschen.de> <57CD3C7A.1000902@maxrnd.com> From: Mark Geisert Message-ID: <57CF3E21.3060901@maxrnd.com> Date: Tue, 06 Sep 2016 22:07:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-09/txt/msg00007.txt.bz2 Hi Adrien, I want to dig a little further into this... Adrien JUND wrote: > I have tried to see how to integrate Dokan in cygfuse and it is > currently hard linked to WinFSP and makes hard the integration for > others FS. > A neutral interface with common operations should be made to fix the situation. Cygfuse is intended to be the neutral interface. I'll be making cosmetic changes to it to make it more clear what belongs to cygfuse and what belongs to FUSE implementation DLLs loaded by cygfuse. Does the strategy of testing something in the environment for existence of Dokan, then if found, load a Dokan-specific DLL sound workable for you? I want to be sure I'm not assuming too much about what FUSE implementations provide. If you can be more specific about the gap between cygfuse as it is now and cygfuse being usable for you, please feel free. You could also wait for a cosmetically updated cygfuse which I hope to have in "a few days" modulo real life interruptions. Thanks much, ..mark