From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m0.truegem.net (m0.truegem.net [69.55.228.47]) by sourceware.org (Postfix) with ESMTPS id 8056F3858D35 for ; Tue, 1 Feb 2022 03:50:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8056F3858D35 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=maxrnd.com Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id 2113obsU062598 for ; Mon, 31 Jan 2022 19:50:37 -0800 (PST) (envelope-from mark@maxrnd.com) Received: from 162-235-43-67.lightspeed.irvnca.sbcglobal.net(162.235.43.67), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpdDM3M7d; Mon Jan 31 19:50:34 2022 Subject: Re: fuse To: Cygwin-Apps References: From: Mark Geisert Message-ID: <7d9cc328-2af9-6171-6407-80e9d7fdcdc8@maxrnd.com> Date: Mon, 31 Jan 2022 19:50:34 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2022 03:50:40 -0000 Replying to myself... Mark Geisert wrote: > Hi Thomas, > > Thomas Wolff wrote: >> What became of the winfsp-fuse project discussed in July 2016? >> I'd like to be able to use ftpfs or sshfs in cygwin. > > Integration of the project into Cygwin stalled around that time, or was it 2018? [...] > I would love to have somebody interested in trying out FUSE on Cygwin.  If you > require a cygfuse package I guess the first step for that would be for me to > reissue the ITP and make the package real.  Another alternative would be for you > to build from the Github repo https://github.com/mgeisert/cygfuse if you're > feeling adventurous. Our fuse package as it stands is not ready for use. When I last looked at it years ago I was too new to both FUSE and project porting to understand what was missing. Currently it's a source package that supplies a glue layer for Cygwin apps to make use of WinFSP, a Windows FUSE driver. It also supplies source for a Cygwin sshfs app that demonstrates correct operation of WinFSP via Cygwin. I've now looked at and installed the most recent WinFSP. The Cygwin glue layer works as well as it always had. But something is missing: integration with the usual shell file manipulation commands. For example, one can't 'cd' into the directory on which a foreign file system has been loaded. That seems like a major issue unless I'm misunderstanding things. Let me reach out to the WinFSP folks and see if I'm doing something wrong or if there's additional work to be done on the Cygwin side. In any case the project needs some smartening up. I plan to rename it FUSE for the upcoming ITP, to avoid name conflict with libfuse* common on Linux. I see that 'mtr' is another Cygwin package that makes use of a Windows driver via libpcap. Maybe I can use mtr.cygport etc as a guide; I'm unsure whether a Cygwin package should be including Windows drivers. Thanks for reading; advice welcome, ..mark