I think that ~/.gvfs is an appropriate location for fuse mounts. If
you want them to be more visible, then do: ln -s .gvfs Volumes. To
have gvfs create a real directory called "Volumes" in the home folder
doesn't seem like the "right" thing to do. To have it mount them in
/Volumes is definitely not the right thing to do. It violates the
linux filesystem hierarchy standard, which, i hope, is still followed.
Linux is not OSX, thankfully. Also, being that it's a user-space tool,
it only belongs in the home folder.
On Mon, May 12, 2008 at 8:40 AM, Sebastien Bacher <email address hidden> wrote:
> what you describe seems to be a vlc issue, it should not claim
> supporting vfs uris if it doesn't
>
>
>
> --
> gvfs fuse mount is not functional after logout and subsequent login
> https://bugs.launchpad.net/bugs/212789
> You received this bug notification because you are a direct subscriber
> of the bug.
>
I think that ~/.gvfs is an appropriate location for fuse mounts. If
you want them to be more visible, then do: ln -s .gvfs Volumes. To
have gvfs create a real directory called "Volumes" in the home folder
doesn't seem like the "right" thing to do. To have it mount them in
/Volumes is definitely not the right thing to do. It violates the
linux filesystem hierarchy standard, which, i hope, is still followed.
Linux is not OSX, thankfully. Also, being that it's a user-space tool,
it only belongs in the home folder.
On Mon, May 12, 2008 at 8:40 AM, Sebastien Bacher <email address hidden> wrote: /bugs.launchpad .net/bugs/ 212789
> what you describe seems to be a vlc issue, it should not claim
> supporting vfs uris if it doesn't
>
>
>
> --
> gvfs fuse mount is not functional after logout and subsequent login
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
:wq