Comments on: Access gvfs mounts from the command line http://www.g-loaded.eu/2008/12/08/access-gvfs-mounts-from-the-command-line/ An open-source software and technology related journal Fri, 03 Feb 2012 18:35:21 +0000 hourly 1 By: Harry http://www.g-loaded.eu/2008/12/08/access-gvfs-mounts-from-the-command-line/#comment-19052 Harry Wed, 26 Oct 2011 02:21:46 +0000 http://www.g-loaded.eu/?p=744#comment-19052 Is this normal?? Or do I have corruption or something else. -rw-r--r-- 1 toto toto 143 2011-09-30 22:56 .gtkrc-2.0 d????????? ? ? ? ? ? .gvfs/ -rw------- 1 toto toto 3380 2011-10-25 17:29 .ICEauthority drwxr-xr-x 2 toto toto 4096 2011-08-06 19:31 .icons/ Is this normal?? Or do I have corruption or something else.
-rw-r–r– 1 toto toto 143 2011-09-30 22:56 .gtkrc-2.0
d????????? ? ? ? ? ? .gvfs/
-rw——- 1 toto toto 3380 2011-10-25 17:29 .ICEauthority
drwxr-xr-x 2 toto toto 4096 2011-08-06 19:31 .icons/

]]> By: Jasmo http://www.g-loaded.eu/2008/12/08/access-gvfs-mounts-from-the-command-line/#comment-12062 Jasmo Wed, 30 Sep 2009 05:05:59 +0000 http://www.g-loaded.eu/?p=744#comment-12062 I discovered this same last night. And it's great finally find the mount point.. Why, why why for gods sake the mount point has to be hidden directory? What is the benefit of that? Is direct access (from shell or so) to .gfvs somehow thought undesireable? I discovered this same last night. And it’s great finally find the mount point..

Why, why why for gods sake the mount point has to be hidden directory? What is the benefit of that? Is direct access (from shell or so) to .gfvs somehow thought undesireable?

]]> By: happynix http://www.g-loaded.eu/2008/12/08/access-gvfs-mounts-from-the-command-line/#comment-12057 happynix Mon, 28 Sep 2009 18:38:50 +0000 http://www.g-loaded.eu/?p=744#comment-12057 Note: if you are not running a windows manager. (i.d. you have ssh-ed into the server/workstation) then you might need to launch gvfs-mount like so: <code>#$ dbus-launch gvfs-mount </code> This will take care of launching gvfs-fuse-daemon, etc. so you won't have to do it manually. (At least on ubuntu w/ dbus installed) Note: if you are not running a windows manager. (i.d. you have ssh-ed into the server/workstation) then you might need to launch gvfs-mount like so:
#$ dbus-launch gvfs-mount

This will take care of launching gvfs-fuse-daemon, etc. so you won’t have to do it manually.
(At least on ubuntu w/ dbus installed)

]]> By: George Notaras http://www.g-loaded.eu/2008/12/08/access-gvfs-mounts-from-the-command-line/#comment-11598 George Notaras Wed, 10 Dec 2008 08:56:17 +0000 http://www.g-loaded.eu/?p=744#comment-11598 Actually, it is possible to use gvfs on a desktop environment other than GNOME, but you have to use the <code>gvfs-mount</code> utility directly as there is no graphical facility like the "<em>Connect to server</em>" feature of the GNOME desktop. For example, connecting to a remote SSH server requires the following: <pre class="console"> gvfs-mount sftp://johndoe@secure.example.org </pre> This will not work though if <strong>gvfsd</strong> and <strong>gvfs-fuse-daemon</strong> are not running in the background. I logged into <strong>fluxbox</strong> and both of those servers had been already running in the background. I didn't have the time to investigate what had started them. I checked the system services but did not see any gvfs-related daemon being started on boot, so I guess they are started in the fluxbox loader script. Anyway, if those daemons are not up, you can start gvfs-fuse-daemon manually, which in turn starts gvfsd. Ensure that the mount point <code>/home/johndoe/.mygvfsmounts</code> exists prior to bringing the daemon up. <pre class="console"> /usr/libexec/gvfs-fuse-daemon /home/johndoe/.mygvfsmounts </pre> This is probably not the optimal way to start this service, because if I kill it and then restart it using the same mount point (.mygvfsmounts), I get an error. Anyway, if gvfsd and gvfs-fuse-daemon have successfully been started, then you can use gvfs-mount to connect to remote services and access their virtual filesystems inside .mygvfsmounts. Actually, it is possible to use gvfs on a desktop environment other than GNOME, but you have to use the gvfs-mount utility directly as there is no graphical facility like the “Connect to server” feature of the GNOME desktop. For example, connecting to a remote SSH server requires the following:

gvfs-mount sftp://johndoe@secure.example.org

This will not work though if gvfsd and gvfs-fuse-daemon are not running in the background. I logged into fluxbox and both of those servers had been already running in the background. I didn’t have the time to investigate what had started them. I checked the system services but did not see any gvfs-related daemon being started on boot, so I guess they are started in the fluxbox loader script.

Anyway, if those daemons are not up, you can start gvfs-fuse-daemon manually, which in turn starts gvfsd. Ensure that the mount point /home/johndoe/.mygvfsmounts exists prior to bringing the daemon up.

/usr/libexec/gvfs-fuse-daemon /home/johndoe/.mygvfsmounts

This is probably not the optimal way to start this service, because if I kill it and then restart it using the same mount point (.mygvfsmounts), I get an error.

Anyway, if gvfsd and gvfs-fuse-daemon have successfully been started, then you can use gvfs-mount to connect to remote services and access their virtual filesystems inside .mygvfsmounts.

]]> By: Dimitris Glezos http://www.g-loaded.eu/2008/12/08/access-gvfs-mounts-from-the-command-line/#comment-11596 Dimitris Glezos Tue, 09 Dec 2008 16:26:26 +0000 http://www.g-loaded.eu/?p=744#comment-11596 Awesome idea about command-line access to GFVS mounted dirs, haven't thought about it until I read your post. GVFS is one of the features I miss the most when I need to temporarily work on another desktop environment for any reason. Another one is, of course, package management. Awesome idea about command-line access to GFVS mounted dirs, haven’t thought about it until I read your post.

GVFS is one of the features I miss the most when I need to temporarily work on another desktop environment for any reason. Another one is, of course, package management.

]]>