delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2016/06/17/10:08:50

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:subject:to:references:from:message-id:date
:mime-version:in-reply-to:content-type
:content-transfer-encoding; q=dns; s=default; b=aJvi6+odVe0chzns
oT5QivLgHalG0YUS2Ff739lxTW660I5w2gNwAvF5I1ZnVvqN35UDIoArK5e2462Y
/6QjpTepMBAckr9T10VwsyfEu2L0moTnfShb1FmiKxneE4RRUzIJKDoIPrpUKUgM
DiqY1+t9+QcoMe9ASQRoSHWAaog=
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:subject:to:references:from:message-id:date
:mime-version:in-reply-to:content-type
:content-transfer-encoding; s=default; bh=s5Zsk94yeYH5f8aWro6mY5
y4XkI=; b=xPz2ZYc1b+2slexjNwn1LG8Ytue1Lajc9lPnlSj/XACNM1MPVo9Ylz
IrKafmOUQn9c7uMe+9NZnL85ht3TIt7R46kDpRpy0v4F1UYjEL5U4MyghPhhRS7/
pzSpwvmaCGWACKdqlf5UwzQYpgahMZptDMIg2WZL8rBgUgPRug7Z0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Saturday, saturday, Hx-languages-length:1518, website
X-HELO: mout.gmx.net
Subject: Re: FUSE for Cygwin
To: cygwin AT cygwin DOT com
References: <D388F238.929F%billziss AT navimatics DOT com>
From: Herbert Stocker <hersto AT gmx DOT de>
Message-ID: <2c26c044-ac38-a02a-7583-0cf6b3cf5f06@gmx.de>
Date: Fri, 17 Jun 2016 16:08:18 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <D388F238.929F%billziss@navimatics.com>
X-UI-Out-Filterresults: notjunk:1;V01:K0:rGv2CMmPNgE=:y5LON+J+gm6GnDhFibf855 ieNUj+NT8uuZWPRTNwaKCP9DNPzj15Y4NAuoMG01l9U7Fr6nFHVg9bzMGAj7iwahk+3Bbixu/ iFkrdqLjvTRvkVcXQHcURSdrYfKZHbZpKGbhAOQP6yNohRVOcmZnw2vilqtIZXIyOOOVEzOqL 4ihP4EQi8NuO0fT1t3AOZ9fKw8HsdrTM6M3Do8CLl1CZW6P+zNwGc1daodG7DGJgaHrg/8jch 93U2Ckn4ltIWxy+KlCuWw413NrDJMHxLUU2j91XWhjZ2USI5ZF1nrG1sd4nXyfxDfb5kWkujs w0YptyAJ0th4+lXK0FylnPsuA+QAAOyX7+1GsQ4W5S2viheHibj7EPu9NKx2dgKtrVieFfCti 9slweK4h/cV1usak7HKFjabw9g67n0g3JiWmglfc9jT7Ws6agu8DpbTLOFtuo+fCiLZZtbk7x p8XfpDcVgy5mn3yUcutO6QfGOlta7/TZQON0i3pQ2aj3dg33xp/hQRNO2nNAttDUybW2/QFb0 nFvpfiweiPSmxCZh45Hx6sGEODwyc4SyToBlXgqp9Cp5mLJYDim7tqkbjPCuUztaZt6pfgofg 89anasw6jlSAuUb6SRDLoB+v+X6qedhd7u75QVaRFBNlG7sbLki3pXG+aOM5qpLnqARzcTvPx 38Y2u6l9g1bcWVTfklTCPP4c3gWV2dtcGKIGltjKHoLV90vd4zg2FR3WStkgRPiqiEDBuG0Dl sDQAAk003kZhinI9IHOxWiCHFsgvOWiakTQpapKDxEW1Hv4RGasFeJ1J+7CGGSD2P78uvgxvn oKkKEqZ
X-IsSubscribed: yes

On 6/17/2016 9:25 AM, Bill Zissimopoulos wrote:
> WinFsp provides three (3) different modes of integration:
>
> (1) Its own native API, which allows a user mode file system to do almost
> anything NTFS can do (with a few exceptions). It also allows for the
> Read, Write and ReadDirectory callbacks to be asynchronous (return
> STATUS_PENDING). I recommend this API for file systems that want maximum
> performance and integration with Windows.
>
> (2) A FUSE (high-level) API for Win32 (i.e. non-Cygwin) applications. This
> is useful if one has a FUSE file system that they can easily port to
> Windows or they do not want any Cygwin dependencies.
>
> (3) A FUSE (high-level) API for Cygwin. As you correctly note many FUSE
> file systems are too POSIX specific (as they were born on Linux/OSX) and
> they only make sense in a Cygwin environment.
>
> I expect that most FUSE file systems will probably go for option (3)
> initially. Then they may want to consider going to (2) if they can
> easily port their core file system code to Windows. Then they may even
> consider (1) if they have needs that the FUSE API cannot support (e.g.
> full support for Windows ACL's).

Hi Bill,

i'm planning to make a suggestion of mode (4). It will be in addition or
instead of (3) and will avoid those issues we touched.
But i can't do it earlier than Saturday evening.

Of course i did read your website before posting this, don't know why i
asked that question about your design this way though.

Herbert



--
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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019