On 2020-02-24, David Wright <deb...@lionunicorn.co.uk> wrote: > > > which suggests a bit of misunderstanding about what gvfsd is. > AIUI it's a daemon (hence the d), and not in anyone's PATH, > which is why you have to find out where it's running from and > what might be consulting the value of GVFS_DISABLE_FUSE. > Also I think the service is called gvfs-daemon (but there may > be other related ones involved).
It seems to run from '/usr/lib/gvfs/gvfsd'. I don't know whether he tried, simply, "export GVFS_DISABLE_FUSE=1" or not (and stopped and restarted the daemon by one of the usual methods); I understood what might consult the value of GVFS_DISABLE_FUSE is the gvfsd daemon itself. >From the man: gvfsd-fuse is normally started by gvfsd(1). In this case, the mount point is $XDG_RUNTIME_DIR/gvfs or $HOME/.gvfs. > As for doing exercises, I don't have gvfs* installed, nor any DE, > so I wouldn't know where to start. > > Drifting a litle, I do remember being surprised how easy it is for > devices to be mounted twice, having had difficulty myself (mount > would complain the device was already mounted). It turned out that, > because the device I tried using was originally mounted readonly, > I also had to set ro in the second mount command for it to succeed. > > Cheers, > David. > > -- "J'ai pour me guérir du jugement des autres toute la distance qui me sépare de moi." Antonin Artaud
