[opensuse] [Leap 42.1] Strange listing in /var/run/user
What on earth is going on with that gvfs listing in the following? loki:~ # ls -l /var/run/user/1000 ls: cannot access /var/run/user/1000/gvfs: Permission denied total 4 (snip) d????????? ? ? ? ? ? gvfs (snip) Even the root account is denied access to that, so I cannot read its contents, nor even change permissions or ownership. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 17 Dec 2015 19:44:25 -0600 Darryl Gregorash wrote:
ls: cannot access /var/run/user/1000/gvfs: Permission denied
A quick search on the above string yields many hits, including this: "/run/user/$uid/gvfs or ~$user/.gvfs is the mount point for the FUSE interface to GVFS. GVFS is a virtual filesystem implementation for Gnome, which allows Gnome applications to access resources such as FTP or Samba servers or the content of zip files like local directories. FUSE is a way to implement filesystem drivers as user code (instead of kernel code). The GVFS-FUSE gateway makes GVFS filesystem drivers accessible to all applications, not just the ones using Gnome libraries. Managing trust boundaries with FUSE filesystems is difficult, because the filesystem driver is running as an unprivileged user, as opposed to kernel code for traditional filesystems. To avoid complications, by default, FUSE filesystems are only accessible to the user running the driver process. Even root doesn't get to bypass this restriction." And this (condensed & paraphrased): 'Gvfs is a GNOME userspace virtual filesystem. The available set of commandline utilities includes: gvfs-cat, gvfs-copy, gvfs-info, gvfs-less, gvfs-ls, gvfs-mime, gvfs-mkdir, gvfs-monitor-dir, gvfs-monitor-file, gvfs-mount, gvfs-move, gvfs-open, gvfs-rename, gvfs-rm, gvfs-save, gvfs-set-attribute, gvfs-trash & gvfs-tree. The file libgvfscommon.so contains the common API functions used in Gvfs programs.' hth & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 17/12/15 09:26 PM, Carl Hartung wrote:
On Thu, 17 Dec 2015 19:44:25 -0600 Darryl Gregorash wrote:
ls: cannot access /var/run/user/1000/gvfs: Permission denied A quick search on the above string yields many hits, including this:
I have to admit that I did not search too deeply, as I encountered this in the midst of trying to resolve my scanner problem. You certainly got a lot more results than I did searching only for "gvfs" :D I don't recall the Wikipedia article giving this much information; then again, see above -- I didn't read it in depth.
driver process. Even root doesn't get to bypass this restriction." What a strange way to do things. This is the first time I've ever encountered such a thing. Are there any more oddities like this, in case I run into them in the future?
Thanks for the info, also to Carlos ER, who replied privately. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 17 Dec 2015 21:47:28 -0600 Darryl Gregorash wrote:
On 17/12/15 09:26 PM, Carl Hartung wrote:
On Thu, 17 Dec 2015 19:44:25 -0600 Darryl Gregorash wrote:
ls: cannot access /var/run/user/1000/gvfs: Permission denied A quick search on the above string yields many hits, including this:
I have to admit that I did not search too deeply, as I encountered this in the midst of trying to resolve my scanner problem.
I completely understand ... BTDT :-)
You certainly got a lot more results than I did searching only for "gvfs" :D I don't recall the Wikipedia article giving this much information; then again, see above -- I didn't read it in depth.
The first time I encountered that 'anomalous' directory, I studied up on it enough to understand what I was seeing. I thought I'd save you a little time by gathering up and including the most salient features in my reply. I'm glad you found it helpful.
driver process. Even root doesn't get to bypass this restriction." What a strange way to do things. This is the first time I've ever encountered such a thing. Are there any more oddities like this, in case I run into them in the future?
As I understand it, it's literally a 'virtual filesystem.' The idea that such an object would be strictly fenced off, requiring use of 'native' tools for accessing it's contents, makes perfect intuitive sense to me. I'm sure other, comparable 'oddities' exist. I just cant seem to recall what any of them are -- I plead fatigue -- it's late here :-)
Thanks for the info, also to Carlos ER, who replied privately.
You're very welcome ... and isn't Carlos great?! :-) regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Carl Hartung -
Darryl Gregorash