From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22061 invoked by alias); 22 Jul 2016 12:53:43 -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 19991 invoked by uid 89); 22 Jul 2016 12:53:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=leader, Marco, offer, quality X-HELO: mail-qk0-f193.google.com Received: from mail-qk0-f193.google.com (HELO mail-qk0-f193.google.com) (209.85.220.193) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 22 Jul 2016 12:53:31 +0000 Received: by mail-qk0-f193.google.com with SMTP id q62so8577544qkf.2 for ; Fri, 22 Jul 2016 05:53:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=C4Axqdi5+2qfdsJ7ajWwB+uK5NTIE0q+mIL1YhZj2Uk=; b=C5ZB3tSM3HjvtLHYWOHW/w9PhYS8xT0kAqjz+Phx10ISi2H5FPpDJYmSQxb9pCe3gl H9FVI1BYg9yiKogb2FXrwi2sPPGhZs8wK9/LKi6RRPy3lDLnMthcJiaT1q8ZkXKR7aDG QmoG0ClmxwpMVWxDNGC0GrCuOCEVFmrEI/I13kf8wRgebmmwL9HY+l97mD1VSm6789L1 Bwt+FehCGYa3UIRIH7N0T/hv1/oS6l7be+9Le6GfXzhgrLCKBKZfcj7Bn6a32ITKdj1M jWtG1QzF17MtKlFY8dSQYCuhWdYDHdQnzwTG2S/VP8dMrV89TOhYuiOznP4QKrNDvejN MWKQ== X-Gm-Message-State: AEkoouvZU669ipuRAlo+v3ep5lnF4g+Zx+WTtBiVqY3wnx2WJIWeUZDH2fjOoW+pFxKrww== X-Received: by 10.55.27.98 with SMTP id b95mr4569109qkb.146.1469192008624; Fri, 22 Jul 2016 05:53:28 -0700 (PDT) Received: from [172.21.188.226] ([149.6.156.42]) by smtp.googlemail.com with ESMTPSA id j7sm7263754qkf.11.2016.07.22.05.53.26 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jul 2016 05:53:27 -0700 (PDT) Subject: Re: [ITP] FUSE 2.8 To: cygwin-apps@cygwin.com References: <20160718081931.GE7018@calimero.vinschen.de> <20160719094102.GP7018@calimero.vinschen.de> <20160720085223.GV7018@calimero.vinschen.de> <20160722075926.GF7018@calimero.vinschen.de> From: Marco Atzeri Message-ID: Date: Fri, 22 Jul 2016 12:53:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2016-07/txt/msg00063.txt.bz2 On 22/07/2016 14:30, Adrien JUND wrote: > Hi, > > Here is Liryna from Dokan-dev community, our project Dokany have the > same purpose of Bill project. > Like WinFSP, it is able to mount FUSE filesystem on cygwin before WinFSP exist. > > I would like to point out that naming WinFSP package "fuse" is not the > right way to integrate WinFSP in cygwin. > > The package is not related to fuse developers or community. > It would make the user believe that the package is an official fuse > project and I am not sure that’s what Nikratio from libfuse would > like. > The package should be renamed winfsp-fuse for give ability of cygwin > users to choose which solution they would like to use. Like > dokan-fuse, cbfs-fuse and other projects that offer the same > service... > All these packages would install their own libfuse for link > compatibility that use their own dependency. > Fuse name should be kept for official port by libfuse or by a future > integration directly compatible with windows kernels. winfsp-fuse is a reasonable name. dokan-fuse also (IMHO) > The official fuse window integration is an official request made by > devs on WPDEV. This request is well placed on the top so it is > probably only a question of time before windows do it in the same time > as the Linux subsystem integration. > https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/13522845-add-fuse-filesystem-in-userspace-support-in-wsl This seems just a wish for the time being. Also our team leader asked for a fork or for more support in the implementation of it but MS have never supported it. :-( > I also would like to point out that WinFSP has absolutely no feedback > of any kind by users and has not been tested on all windows versions. > I think Kernel drivers should at least have some feedback and known as > used in production before choosing to be distributed as cygwin > package. > Unstable kernel drivers can create severity damage in case of BSOD > like windows or user file corruption. > > These analyses are probably severe but for the good of cygwin users, > integrate kernel driver dependence should be well thought before > making the step. > > Thanks, > Liryna In general accepting a package is not endorsing its usage or quality. We leave that to upstream responsibility, like it was for libusb. Regards Marco