On 6/25/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
DJ Lucas wrote these words on 06/25/06 12:51 CST:
> automounting intricacies of hal/dbus/gnome-mount
dbus/hal/gvm/gnome-mount :-)
I've not updated the book yet, but the key is to bypassing the
PAM consolehelper stuff using a switch to either gvm or gnome-mount.
I've got to go back and catch up on some of Dan's emails where this
is explained.
This is a bit off the cuff, but here goes.
1. HAL needs to be told about a group or user that can invoke methods
besides root and at_console. Look at /etc/dbus-1/system.d/hal.conf.
There should be sufficient comments there to figure out how to add a
group policy with whatever group you want.
2. gnome-volume-manager needs to be configured with
--disable-multiuser. Otherwise it goes looking for the pam_console
droppings in /var/run/console/`uid -un`.
3. Anything you want auto-mounted can't have an entry in /etc/fstab.
HAL will ignore these for the purpose of auto-mounting.
4. gnome-mount is not strictly needed, I don't think.
gnome-volume-manager and nautilus both have fallbacks to do the
mounting themselves. The benefit of using gnome-mount is that you're
using the mount methods in HAL with all the policy there.
If anyone is interested in pam_console, let me know. It's not
difficult to get set up. Debian has also created pam_foreground which
is very similar. I haven't tried it yet.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
