Re: haldaemon bootscript

Randy McMurchy wrote: Thanks for the catch. I managed to update the script on my test box, but I never even once thought about the bootscript tarball. I fixed it just now. BTW, --daemon=yes is the default so only --use-syslog is needed. Cool. Updated locally and works AFAICT. I didn't see

Re: haldaemon bootscript

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

Re: haldaemon bootscript

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

Re: haldaemon bootscript

Dan Nicholson wrote these words on 06/25/06 13:26 CST: 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. I'm guessing that in order to use pam_console, the system must be

Re: haldaemon bootscript

On 6/25/06, Randy McMurchy [EMAIL PROTECTED] wrote: Dan Nicholson wrote these words on 06/25/06 13:26 CST: 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. I'm

Re: Broken links in 25 June 2006 svn

[EMAIL PROTECTED] wrote these words in blfs-book on 06/25/06 15:29 CST: There's a number of broken links in the gnome section, Thanks for pointing this out. I am going through the additional GNOME packages now and cleaning up. I overlooked the gtksourceview link. I'll fix that one before next

default config for hal/gvm without pam_console/pam_foreground (Was: haldaemon bootscript)

Dan Nicholson wrote: 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

Re: default config for hal/gvm without pam_console/pam_foreground (Was: haldaemon bootscript)

DJ Lucas wrote: !-- Allow anyone in halusers group (gid 61) to utilize HAL -- policy group=61 allow send_interface=org.freedesktop.Hal.Device.SystemPowerManagement/ allow send_interface=org.freedesktop.Hal.Device.LaptopPanel/ allow

Re: problem whith KDE.3.5.2 and xorg 6.8.2

Carlos Eduardo de Brito Novaes wrote these words on 06/25/06 17:42 CST: this is the Errors log when KDE start: running as realtime process now (priority 50) /opt/kde-3.4.1/bin/artsd: No such file or directory Here you got a real problem. kde is looking for kde-3.4.1... I think you forgot

Re: default config for hal/gvm without pam_console/pam_foreground (Was: haldaemon bootscript)

On 6/25/06, DJ Lucas [EMAIL PROTECTED] wrote: DJ Lucas wrote: !-- Allow anyone in halusers group (gid 61) to utilize HAL -- policy group=61 allow send_interface=org.freedesktop.Hal.Device.SystemPowerManagement/ allow send_interface=org.freedesktop.Hal.Device.LaptopPanel/

Re: default config for hal/gvm without pam_console/pam_foreground (Was: haldaemon bootscript)

On 6/25/06, DJ Lucas [EMAIL PROTECTED] wrote: Gravy! It just works! Cool. Without looking too hard, something similar might be good for the default configuration without pam_console or pam_foreground (need to review security precautions): groupadd -g 61 halusers cat