Hi all,
After now a couple of days (only a couple of hours total, however),
I cannot get the advertised capability of D-BUS/HAL and a userspace
tool to work. What I mean is, I cannot get a device to be mounted
automatically.
Does anyone have the necessary adjustments/additions I need to do
to the default HAL storage policies for this to work?
I would like to get HAL into the book, but I would also like it to
do what it is advertised to do.
Here is what I have so far:
1. D-BUS installed according to BLFS (starting the session daemon
via 'exec dbus-launch --sh-syntax --exit-with-session gnome-session'
in .xinitrc and using "startx" to launch GNOME-2.12.0)
2. HAL-0.5.4 installed using the following configure line:
./configure --prefix=/usr \
--sysconfdir=/etc \
--libexecdir=/usr/sbin \
--localstatedir=/var \
--enable-doxygen-docs \
--enable-docbook-docs \
--enable-fstab-sync \
--enable-pcmcia-support
3. Starting the HAL daemon as the root user as such:
hald --verbose=yes --daemon=yes --retain-privileges
(I realize the --daemon=yes probably isn't required)
I am passing --retain-privileges as I'm thinking this is required
for the fstab-sync program to work properly.
4. I have gnome-volume-manager installed.
5. I have tried with and without fstab entries for the devices I
am plugging in: usb disks, and a cdrom with linux partition (actually
an LFS-Live-CD.
6. I have attempted to modify the policies just a bit to no avail.
Here are my findings:
1. Gnome-volume-manager allows me to mount the devices with a simple
click on the appropriate device in the panel applet. I can unmount
them the same way. This creates a desktop entry for the device (to
browse the contents), and works as expected. However, I think the
mount should be automatic when plugging in the device.
2. The above only works if I have proper entries in /etc/fstab for
the devices. Without entries, gnome-volume-manager complains that
there are not appropriate entries. My understanding from reading the
HAL docs is that the fstab-sync callout program should automatically
create fstab entries.
3. hal-device-manager properly discovers all the devices, but only
if the hald daemon is started after the devices are plugged in one
time. Until I have the devices plugged in, and start the hald daemon
at least one time this way, the devices do not get shown in the
hal-device-manager display.
4. I don't know if I'm supposed to get messages from the system or
session D-BUS monitor when plugging in a device, but I don't get any
messages. Using dbus-send I can send messages that are displayed by
dbus-monitor.
5. I cannot figure out if, and where, D-BUS and HAL logs anything.
Any help from someone that has more experience with D-BUS/HAL would
be appreciated. My apologies for the long post and my ineptitude
with figuring this stuff out on my own. I have tried, but my
frustration level at this point is quite high, and perhaps someone
can offer some constructive advice.
--
Randy
rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3]
[GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686]
10:16:00 up 4 days, 18:40, 3 users, load average: 1.29, 1.06, 0.69
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
