HAL/D-BUS - 1 more time
dbn.lists at gmail.com
Tue Apr 25 07:29:33 PDT 2006
On 4/25/06, Randy McMurchy <randy at linuxfromscratch.org> wrote:
> I'd like to revisit the HAL issue again to see if there is any more
> news or information regarding it. Most people that have commented so
> far simply say "All you have to do is use the new GNOME auto-mount
> program (I've forgotten its name), and everything will work the same".
I can't say how this works in gnome-2.12, but the new setup with
gnome-mount in 2.14 is working well for me.
> To clarify, when I say "automount", I don't mean that the device
> needs to be clicked on in the GUI desktop or some other manual
> intervention required to access it, I mean it is *automounted*.
> Which means mounted immediately upon insertion, without any manual
This is what Juerg was referring to as mount-on-demand. It is
something different, although the newer gnome is clearly using the
enhanced device data from HAL. So, it is something different.
> With the current BLFS HAL setup, which uses the fstab-sync method of
> updating /etc/fstab in the automount process it works in KDE.
> My question is, how is this going to work now in KDE when there is
> no longer the fstab-sync operation to update /etd/fstab? I don't
> want to update HAL/D-BUS and have GNOME work great but KDE
> automounting broken.
I have no idea, but I'm sure it will be taken care of in the future if
not already for KDE. The way it works in the newer HAL/gnome-mount
setup, fstab isn't touched. In fact, I had to comment out all of my
removable devices in fstab to make it work.
I wouldn't update HAL beyond the version where fstab-sync is removed.
I don't think that gnome-2.12 would work without it, but I'm
speculating. Joe pointed out that things stopped working for him when
he updated to the newer HAL without fstab-sync. Newer HAL requires at
least some helper program to actually handle the mounting. HAL just
exports information about devices/volumes/permissions, etc.
Here's a KDE wiki page showing how to use HAL/D-BUS with ioslave. It
suggests using pmount if you don't use fstab-sync.
Here's a guys blog that suggest using pmount and kdebase-kio-plugins
It also looks like William is not off base using ivman. It's
suggested in a couple pages I've seen, but I've never tried it.
> KDE is being run by user A on machine X. However user A is not
> *using* KDE at the moment, instead user A is also logged into
> machine X via SSH on some other machine. When a device is plugged
> into a USB port, or a CD inserted into the drive, of machine X
> (even if this required a phone call to a person who had physical
> access to machine X if User A does not at the moment), it becomes
> available system-wide, without any interaction in the GUI desktop.
This is a guess, but in that setup with the newest HAL, probably
pmount is the way to go.
Without pmount, I think you need fstab-sync. I've never tried much
outside of a gnome-session with gnome-volume-manager running. I'll
play around and try to figure out if there's a simple way to get
automounting going through HAL without it.
My suggestion for right now since we are about to cut a testing branch
is to leave HAL at the newest version with fstab-sync and the newest
D-BUS that it's compatible with. At least one package would have to
be added in the absence of fstab-sync. Although, it appears that
pmount would work with older gnome-volume-manager, judging by the date
of this post:
More information about the blfs-dev