From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 59787 invoked by alias); 5 Sep 2016 09:36:18 -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 58000 invoked by uid 89); 5 Sep 2016 09:36:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.6 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=UD:cygport, cygwin-apps-owner@cygwin.com, cygwinappsownercygwincom, U*cygwin-apps-owner 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; Mon, 05 Sep 2016 09:36:05 +0000 Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id u859a4pu065733 for ; Mon, 5 Sep 2016 02:36:04 -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 smtpdhM5czM; Mon Sep 5 02:35:54 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> From: Mark Geisert Message-ID: <57CD3C7A.1000902@maxrnd.com> Date: Mon, 05 Sep 2016 09:36: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/msg00002.txt.bz2 Bill Zissimopoulos wrote: > Mark, hi: > > On 8/22/16, 12:43 PM, cygwin-apps-owner@cygwin.com on behalf of Mark > Geisert wrote: > >> I'm debugging some faulting test programs so this cygfuse code doesn't >> seem fully ready for prime time just yet. I'm sure Bill had it working >> so >> it's likely to be some kind of local issue, so it's mine to solve. > > While still on vacation I now have reliable access to the Internet and am > able to follow up on any issues. Please let me know what the issue you are > seeing is and I will try to help. Sorry for the delay. I've 'git clone'd the cygfuse repository and have been poking around, building and testing things. 'make cygfuse-test.exe' does build a cygfuse-test.exe but running it yields a core dump. Exit status is 134. I'm just running it without any args. Is that abort a symptom of not having the WinFSP driver loaded, or something else? Cygfuse works for both 32- and 64-bit Windows environments, right (assuming you're running the correct one)? Separate from that, it's been a little work disentangling the meaning of various names used for this project. Here's what I think the names mean: FUSE - a protocol, which exists in different versions WinFSP - a Windows-native DLL mapping FUSE 2.8 ops to/from Windows file ops cygfuse - a Cygwin DLL allowing Cygwin SSHFS and FUSEPY to use WinFSP If that's correct, I'd like to regularize the names of things in the proposed cygfuse package to accurately reflect their meaning. E.g., change fuse.cygport to cygfuse.cygport, etc. The doc inside some files might need updating. I wasn't sure from Corinna's comments a while back (re hosting this package) whether she thought cygfuse should be part of Cygwin, as in placed in the Cygwin source tree, or just conveniently hosted on the Cygwin GitHub area. That's where I'm at. Thanks for reading. ..mark