Anton Aylward wrote:
Michael Powell said the following on 04/14/2011 05:33 PM:
Also keep in mind that UDisks and UPower are generalized as replacements to HAL. Probably shouldn't try having both on the same system, e.g. a one _or_ the other.
Help me here. Is there something that says _definitive_ to use one or the other?
No, I don't think so. I have just had occassional glitches in the past when competing system changes overlapped one another. Even now, if I use the Dolphin GUI context menu option to "Eject disk" my CD-ROM will open and close without stopping to allow me to take the disk out. Yet using the command line instead: udisks --eject /dev/sr0 behaves correctly. So evidently KDE has a glitch in it's use of UDisks. Growing pains... I do not know enough about the subject, but from what I recall the freedesktop.org project was designed so there would be a common abstraction layer for use between various different GUI desktops and underlying OS. This would enable stuff like people who use KDE to also have Gnome applications useable on their system with minimal friction (theoretically).
# rpm -q --whatrequires hal libnjb-2.2.6-96.2.i586 libkde4-4.5.5-1.3.i586 xfce4-power-manager-0.8.4.2-3.2.i586
My system is openSUSE 11.4 and KDE 4.6.2. The same command on my box yields: no package requires hal And yet when I look at installed packages HAL is still installed.
# rpm -q --whatrequires udisks libgdu0-2.30.1-1.38.i586 pm-utils-1.3.0-10.3.1.i586
And again: testuser@workstation:~> rpm -q --whatrequires udisks libgdu0-2.32.0-5.1.x86_64 kdelibs4-4.6.2-391.3.x86_64 ^^^^^^^
And I was under the impression that ivman dealt with things like usb sticks and pcmcia cards
I wouldn't know; have never had nor used ivman.
From man ivman
<quote> Ivman, or Ikke's Volume Manager, is a daemon to handle the mounting of media as they are inserted/attached to the system. It can also be used to execute arbitrary commands when a device with certain properties is added to the system (Windows autoplay style functionality),and to execute arbitrary commands when device properties change. Ivman uses HAL to monitor the state of your system's hardware. </quote>
So wnat is invovled in switching over from hal/ivman to udisks ?
It is up to whoever writes/maintains any particular application as to which supporting library he/she wishes to link against to pull in external function support. Typically this is not something the lowly end user has much say about. The developers and packagers will be more involved in any kind of changeover and if they get it right it should "Just Work" for the end user. Dependencies will follow which ever external library(ies) a developer has chosen to link his/her application against when it is compiled into a binary executable. -Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org