Date: Sun, 21 Mar 2021 21:43:57 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 254452] [fusefs] [devel/gvfs]: gvfsd-fuse needs FUSE_CAP_ATOMIC_O_TRUNC from fuse Message-ID: <bug-254452-6497-tPRXN2L5dp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254452-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-254452-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254452 Alan Somers <asomers@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Not Accepted --- Comment #1 from Alan Somers <asomers@FreeBSD.org> --- Unfortunately it isn't possible to implement this feature in FreeBSD. The = VFS abstraction hides that information from the file system. It only works in Linux because Linux doesn't have any kind of VFS. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236340 for more discuss= ion.=20 My recommendation is to find out why gvsd-fuse thinks it needs that flag. = It probably doesn't. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254452-6497-tPRXN2L5dp>