Re: Where are the local GVFS mounts?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2014-02-23 05:15, Mike Toews wrote:
> Hi,
>
> I have mounted a smb share through the convenience clicking through
> of Gnome's Nautilus browser. Great! However, I cannot seem to do
> anything with it from a terminal. The properties (again, from
> Nautilus) don't say where the local mount is, and the "Open in
> Terminal" extension is not available for any of these directories.
>
> Digging though similar questions and the technology behind, I have
> discovered this was made possible with GVFS:
> https://wiki.gnome.org/Projects/gvfs/doc
>
> which says: "The default mount point is /run/user/<UID>/gvfs,
> usually located on tmpfs, with a fallback to the old location
> ~/.gvfs when not available."
>
> On my Debian Wheezy 7.4 (amd64) where I'm having this difficulty,
> these directories do not exist:
>
> /run/user /var/run/user ~/.cache/gvfs
>
> And this directory is empty: ~/.gvfs/
>
> And the smb mount is not found here: /media/ /mnt/
>
> But, from the same terminal, I can see that there is a GVFS mount:
> $ gvfs-mount -l ... Mount(0): sharedir on wincomp ->
> smb://wincomp/sharedir/ Type: GDaemonMount
>
> So where is the local mount that I can use with a shell? Why is it
> so obscure to find?
>
> This is my same question: http://superuser.com/q/717893/79304
>
> -Mike
>
>
IIRC, I had to install gvfs-fuse, add myself to the fuse group, log
out and back in; then I could access gvfs in
/var/run/user/$MY_USER_ID/gvfs.
NB: I use sid, so YMMV.
Update: I just looked at the superuser question, and it seems to have
received the same answer I'm giving here. Except that w/ wheezy, gvfs
shows up in ~/.gvfs instead of /var/run/user/$MY_USER_ID/gvfs.
- - Felix
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCgAGBQJTCfyDAAoJELIY/ywn/GzGm8YP/jhNEyZuxRgXoVcWS67NkJzx
pR9UQn5CbeKFBl1Sl+gu5IILI0UeYeZ1U0WUAJweCbUUn9MhB7T2q6HGzSnbEDzG
0xosCeQMd8mSyDGPCYegnsFdpFeFBaQmyflNV6nt6dWVxwfa4YyxEWh53NwPIOM8
k0NjPKY4FJmcVvKRwavp0t6erd6+GDLfRTNWjeWP3STPzsBRcnLP75EqOquQDwzi
MtWR8MY8hzCKH8VSMnGx0gYy8klWTX7xO6oFyCfjeZBgwqPK2iYAWjg3m6SVexfp
xnSll/pd2VLRlIfFB2Xsm5mA943wtOe4KdQgCyRKf3aJoHqaYVpYtb6V7c54Kwfq
qkiM6Om+qpAjRVzVOtd19HTZonYUzj9lnidiCGKg+UgxXZqQqraRVO22b/VLQQvJ
AX+GBiI+Dl+Khf8RESTuVY8DxgtCZ1vJs1wHuaKkSM5uhY0X1UUSXSzFmJoAfbYp
sz29b4a2adewMXJTSTS6Pw7k4vSur8CdIzwHOTwP70ze2NEyJTQZJ2uuYoRqSNGg
J/qFK+eMqUdG+9yzg1au7gLn8yHQ/y8flIAF7LgmevtakdxJxR3s4Hii2Ysnbu8H
l9IO8g7Y68F6kmJ5UlBGL5TLmEwWJ1o872UUw0Lv4tPVPx4sxzxfL3HVNzWnH4bI
AUj0VrMwRb9T21KHzOvs
=Kc0C
-----END PGP SIGNATURE-----
Reply to: