On Sunday 01 April 2012 20:36:49 you wrote:
Udisks? Vincent in this tread said it is possible to mount via sending dbus messages to udisks. Udisks is a daemon, but currently automounting requires additional daemons besides udisks and udev. I'm pretty sure that's exactly how things work today on the gnome desktop, right?
In KDE 3 and 4 a kded module is responsible for listening to udev and applying automount policy.
And KDE3's kded currently does not know about udev and the listening is done by another daemon (this may change soon).
Anyway, all functionality for automounting is already existing in udev so there is no need in wasting resources of a desktop for listening anything. Just write the automount policy in udev and all will work by itself.
the powers that be have decided this a bit different :)
- udev is conceptually for creating device nodes and tagging the devices - udisks is the service that abstracts mounting towards desktops etc.
Mounting is done by desktop agents... - gnome GVFS - not sure about KDE4
and background mounting with - udisks-glue e.g. is a system daemon that implements automount policies.
So udisks-glue is a completely superfluous creature that doubles the functionality already existing in udev. Not to say its huge resources consumption (much greater than devmon automounter, for example), linking to a huge external library libconfuse, need for an extensive .conf file that doubles the purpose of the file /etc/udev/rules.d/81-mount.rules, with its own unique syntax. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org