DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 543KOu0n3840256 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 543KOu0n3840256 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=npEE/dTl X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 712733858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1746303894; bh=3ITlNK8L7PXEco21p9GcnEie4A+1+BhLsV9xIQ56DWk=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=npEE/dTlhpnM2kJq0VmLvKPuVMh1ngX0ntgOCurPl9GrDRD5qfvpITQJSPcxK1iiw x8PK6X/yCJp4EIfPtCX+iS2Bj2b8RQznvfLu8dPvzoMtWTHDOJXHarmtP8tABybwhb a80J6rmdGV+uDlkmApm/Mye4KhV97ushR4wVetJs= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A79DA3858C42 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org A79DA3858C42 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1746303868; cv=none; b=BAgSNQmnfRfJtqS6Q88FQbLZ0bK7e9LG3IM5YsVLdFYgtlPjU24fmJhP24l1XalyyPd3RL8lmEiQoG3B8DbfNnesjGKVHu35veOToM0XBHeRMNunT6Ro9z0HTFp1R3e6KjZ8Bb8hw/tUyvNKMfz9JSEvfGddii6OcnK599njgkI= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1746303868; c=relaxed/simple; bh=HlE4xNlrz0tim2/3hQLyedG0+16D7PM5RD7HYJGUTY0=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=n8ojGwtItF78TdpFsOGv2WZaH2Nz3MdeGcokBbLNb/BVWDZb+fNCEK9RYrQx1z5fTvJ/c9sdSGx80R2K0jXJsR3pLBJwQyS+qvtvOZATD+xzVKOwEJnfiXYor0UVhUnw3Px7Weh/dB+Uak5s/0Ks2GAcQ1G9GcbCiFnD5rtQZEI= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A79DA3858C42 Message-ID: <97ecd208-026d-4e2f-a1f6-cdcf17457de6@holgerdanske.com> Date: Sat, 3 May 2025 13:24:16 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: fstab and sshfs To: cygwin AT cygwin DOT com References: Content-Language: en-US In-Reply-To: X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: David Christensen via Cygwin Reply-To: David Christensen Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 543KOu0n3840256 On 5/2/25 22:15, Mark Geisert via Cygwin wrote: > Unfortunately Cygwin hasn't integrated FUSE filesystem types into > 'mount' and /etc/fstab.  This is why FUSE mounts are recorded in /var/ > run/fuse.mounts rather than in the usual mount table, for example. > > The sshfs man page is correct for Linux and other OSs but less so for > Cygwin.  On Cygwin any FUSE mount has a managing process; these are > sshfs, and when available, ftpfs, memfs, etc.  They do the actual mount > and then hang around in background to support operations on the mounted > filesystem.  The Cygwin DLL doesn't know about these filesystems. > > If your goal is to have "permanently" FUSE-mounted filesystems, about > all I can suggest is to run sshfs from your first Cygwin shell after a > system boot. > HTH, > > ..mark Thank you for the clarification. David -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple