Using a Read-Only Persistence Capability in Knoppix LiveUSBs

[Werner P. Schulz]

Excluding .gvfs may be a good idea; it may louse up the command.
This annoying file may or may not be hanging around to cause trouble.

'~/.gvfs' isn't a ordinary file; it is the mountpoint for GVFS. Therefore you cannot delete or copy it.

http://en.wikipedia.org/wiki/GVFS

[utu]

Greetings, Werner, nice to hear from you.

I've been reading about this (.gvfs) some.

It turns out, as you say, that .gvfs is a mount point put there by some program,
possibly LibreOffice, which I use. In my case the .gvfs, as a file, never has any contents;
it does show up as in an mtab entry related to fuse.

One post I read suggests unmount and delete and see what happens.
The notion being is that if some program needs to mount something it will re-
establish the mount point. I'm trying this route at present.

FWIW, Ubuntu and others are re-routing this mount point to what we would call /run/knoppix/.gvfs,
all with no more explanation than for the earlier home directory location.
Users have been perplexed by .gvfs for as far back as 2008 I've noticed.

[Capricorny]

'~/.gvfs' isn't a ordinary file; it is the mountpoint for GVFS. Therefore you cannot delete or copy it.

http://en.wikipedia.org/wiki/GVFS

All my self-created mount points can be deleted when not in use. And nothing seems to be mounted on my .gvfs, still there is no way to modify it using the ordinary file system commands. So .gvfs is something else, to me seemingly introducing new system features in userspace.

Maybe no wonder Miguel de Icaza is now a dedicated Mac user...?

[utu]

Greetings, Capricorny.

AFAICT, PCMan needs fuse to do something with policykit in creating LXDE,
so gvfs comes in with PCManFM. You can unmount and delete .gvfs, but it
will re-appear after a while. It is annoying, but appeals to both PCMan and
Klaus K will have been of no avail up to now.

Also, FYI, Ubuntu has re-located this annoyance. See:
http://askubuntu.com/questions/21141...n-ubuntu-12-10

[Capricorny]

Greetings, Capricorny.

AFAICT, PCMan needs fuse to do something with policykit in creating LXDE,
so gvfs comes in with PCManFM. You can unmount and delete .gvfs, but it
will re-appear after a while. It is annoying, but appeals to both PCMan and
Klaus K will have been of no avail up to now.

Also, FYI, Ubuntu has re-located this annoyance. See:
http://askubuntu.com/questions/21141...n-ubuntu-12-10

Of course, PCMan doesn't want to break Gnome, which, AFAIK is used several places in LXDE. And Klaus K wants to stay as compatible with the major desktops/APIs as possible. So they should not be expected to be positive. The trouble is with the GIO implementation, I think - KDE's version, KIO, does much of the same, but AFAIK without creating such problems.

[utu]

The trouble is with the GIO implementation, I think - KDE's version, KIO, does much of the same, but AFAIK without creating such problems.

I think you have got it right, but I can only guess that a kde approach
must have some downside like requiring more infrastructure to be brought in
to enable fuse that outweighs the known gnome .gvfs annoyance.
See: https://bbs.archlinux.org/viewtopic.php?id=92957

[Capricorny]

I think you have got it right, but I can only guess that a kde approach
must have some downside like requiring more infrastructure to be brought in to enable fuse that outweighs the known gnome .gvfs annoyance.
......

Maybe, but I'd guess it is more of a cultural thing. Real programmers don't use C++, you know.
FUSE = FileSystem in User Space is actually entirely independent of GNOME, gvfs is just kind of implementation that some think should long have been forked..