Future and impact of ongoing projects in Linux world

[Daniel Llewellyn]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09/10/16 19:53, Xen wrote:
> I am pretty sure that any application that does not support GVFS
> will not see those mounts so easily. You will have to symlink them
> and that defeats the purpose of the system in a certain sense.
> There is no default system that everyone can use

You're quite right that the two incumbents don't recognise each
other's mounting mechanisms. With the gvfs system I do successfully
use the command-line to access the mounted filesystem, which suggests
that KDE applications should be able to access also. I believe the
problem you encountered is due to the daemon that gvfs-mount talks-to
isn't running (is it called gvfsd?), which you _might_ be able to
manually invoke in your KDE session, but I'm not sure on that - there
might be other dependencies that need to be running (dbus-services and
the like..?).

As a feature request that you could try to get implemented by the
gnome guys you could suggest to their issue-tracker that gvfs support
KIO-slaves. Also would be worth suggesting to the KDE guys the
inverse, for KIO to support gvfs-mounts.

I sense the best overall solution would be to unify the daemon-side of
both KIO and gvfs into a single daemon that both desktops back-onto,
but I wonder about how much pushback or otherwise such a unified
effort might encounter from both camps, and others. I bags the name
GKVFIOS and GKVFIO (hybrid nomenclature between GVFS and KIO :-p).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX+pelAAoJEFx8XrpDpVlRL88H/R8eYeiHgwPzysRUC7l+E1ZX
NyTwGKr6WLcaCs2wryayGekjaWYCFGisL8AJBi87VbaGZncTfs2BuMjTIM7AG1St
wMRYky6PMr/trhyXk0PrK4CZY8BGFB65JvINpec1IBNF4v39UesBFsXBGLDuSeJ5
zxyhVKtJB0EodZS+b6ffQqSsETR5mDcBEG4SlTPaTnDpc3s36rCNEmD8Hq8ncU+y
H/arNEd9M/kamkL1jrd4FTbYe+6ks2vkGA6ADini9paXJXsO+6ZA8jT4sVZiAArX
eWIXV+MGCbvjno0YDfJm/Wt8SEaa2nWtWFizxQ7TjpRV4FphhqINjFqBmDqqmmA=
=t6NQ
-----END PGP SIGNATURE-----