Talk:GVfs

Computing: Software Stub‑class Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).

Computing Stub‑class Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the project's importance scale.

What the...?

After reading this article, I have no clue what GVFS is about. Can somebody write a short introduction and not just refer to GnomeVFS? FAThomssen (talk) 10:15, 30 September 2008 (UTC)[reply]

GVFS is an abstraction layer, that allows software to work with different physical or virtual filesystems completely transparently. Some software might just use kernel drivers directly to work with specific filesystem, but GVFS allows higher interfaces, requiring less code duplication and more abilities. It has nothing to do with HAL/udev etc - those are hardware event signalers. 77.180.80.248 (talk) 01:03, 10 April 2014 (UTC)[reply]

Me too. All I know about this GVFS is that it is causing all sorts of crazy errors ever since I upgraded my computer. The main thing I want to know is how to get rid of it. But some explanation of what the people who made it were thinking might help. 68.110.107.158 (talk) 00:45, 14 December 2008 (UTC)[reply]

I agree, this is very badly written. From the current description it appears that gvfs provides file-browsers and other similar applications the ability to browse more that local or network file systems: things like the HAL device tree, or files accessed via ssh or FTP. The file-browser application has a unified view of these virtual file-systems via a shared library, but each backend (for HAL or FTP or whatever) is implemented as its own separate daemon process. The shared library and the daemons communicate via D-Bus, and the integration with FUSE allows any application to see and interact with these virtual file-systems without being specially written to use the gvfs shared library. ...or something. ghw=87.113.55.244 (talk) 19:12, 17 February 2009 (UTC)[reply]

Six years in and still it appears nobody has bothered to, or can, explain what good this thing is or why we should tolerate all the new errors and crashes it introduces. Why do I want "an abstraction layer" when I'm just trying to open a local file on my ordinary hard disk -- much less another daemon running all the time? The "man page" for gvfsd says pretty much the same collection of nothing. I don't like it, I don't want it, it causes me problems for no value added. Why is it there? How can I obliterate it? Someone who knows something about this thing please explain. 68.110.104.114 (talk) 01:37, 2 December 2014 (UTC)[reply]