Randy McMurchy wrote these words on 09/30/05 22:51 CST: > The first pass of HAL-0.5.4 has been committed to BLFS. I do have > some issues that required some input from the group: > > 1. I'm passing the --retain-privileges option to the hald daemon > program in the bootscript. I cannot see how the magic auto-updates > to the /etc/fstab file can take place without it. Am I wrong here?
No replies so far, and as far as I can tell it is required if you want devices to be auto-mounted. --retain-privileges will stay unless somebody can provide a compelling reason to not use it. > 2. Using the --retain-privileges option means that the daemon runs > as the root user. At this point, I don't really see the need to > create the haldaemon user and group. Anyone have a different opinion > here? Still looking for some input here. > 3. I don't list any configuration steps or examples of modifying > default policy. If anyone can provide examples of needed > configuration, I'll be happy to update the book. I have so far needed to: 1) fix the broken LFS hotplug implementation by adding a UDEV rule to run the /etc/hotplug.d/default/default.hotplug script so that required kernel modules will be auto-inserted upon plugging in a device. 2) add a UDEV rule to run the hal.hotplug program 3) tweak the storage policy to remove the 'manage' and pamconsole' mount options so that the devices will auto-mount > 4. It is difficult to test HAL right now, as apparently the LFS > book UDEV/HOTPLUG installation is broken. LFS needs to be updated. The previous comments to #3 make it where I've now tested and confirmed proper operation of HAL. My testing is using GNOME's gnome-volume-manager as the userspace tool to do the auto-mounting. It works just fine for me now with the configuration changes I've made. > 5. I'm recommending that the usb.ids file be downloading from > linux-usb.org. Apparently HAL will use this file if it is installed. > Right or wrong? Still looking for input on this one. > Thanks in advance for any additional input about HAL. Ditto this. One additional comment. I cannot get gnome-volume-manager to automatically bring up a Nautilus browse window when a device is plugged in. Though it is advertised, and an option exists in the configuration to do this, I cannot get it to work. It puts an icon in the gnome-volume-manager panel outlay, and puts an icon on the desktop, but I cannot get a Nautilus window to automatically come up allowing me to immediately browse the contents of the just-inserted device. Any suggestions from folks that have this working would be appreciated. -- 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] 20:15:01 up 7 days, 4:39, 3 users, load average: 1.22, 1.04, 0.67 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
