-   Slackware (
-   -   HAL, DBus and Policykit (

slothpuck 01-30-2007 06:33 PM

HAL, DBus and Policykit

I am running slamd64, which is a 64-bit version of slackware 11 on a normal standard 64-bit PC . However I am having a problem in setting up HAL,DBus and Policykit.

I wanted to run the brand-new XFCE4.4 on slamd64, but there are no packages availiable for 64-bit (32 bit packages won't work, as there are dependencies which involve HAL,DBus and policykit) so I had to compile from source. While I can compile from source ok I'm at a loss as howto set up HAL,DBus and Policykit. A Search on the internet with google turned up bits of information for different distros, but none for slackware. I have managed to successfully compile XFCE4.4 and its dependencies.

I can get to the point where a USB memory stick is automatically mounted (and unmounted; I get an icon on the XFCE4.4 desktop) but I cannot get my cdrom drive to do the same (not mounted, no icon). Can anyone point me in the direction of some config files for slackware or a HOWTO of somesort in order to set up these programs?

Sometimes I do get a cdrom icon from XFCE4.4 if I start with a cdrom in the drive, but once ejected it won't ever "see" the cdrom drive again (no icon, drive never mounted). Also sometimes the cdrom icon won't go away, and remains on screen (even if there's no cdrom in the drive). If I choose eject (in XFCE4.4) under these circuimstances, I get an error "device to unmount is not in /media/.hal-mtab so it is not mounted by HAL".

I'm running the commands polkitd, rc.messagebus start and rc.hal start in that order in my /etc/rc.d/rc.local . I've tried removing the cdrom drive from /etc/fstab as I read that HAL/DBus/Policykit won't mount it if it's in the fstab, but to no avail. All the files in /media look ok, such as /media/cdrom for example.



H_TeXMeX_H 01-30-2007 06:55 PM

might wanna try this:



Just prior to announcing the presence of a device object, operating system specific programs may be run to configure the base operating system. For example, for an unprivileged user to mount a file system, an entry must be added to the file system's table file /etc/fstab. In HAL, this is achieved through a callout — any program (or symlink to a program) in the /etc/hal/device.d/ directory is run whenever a device is added or removed. On Fedora Core 3, this applies to the fstab-sync program. The sole purpose of this program is to modify /etc/fstab when a mountable file system on a storage device is added or removed to the system. For the Compact Flash reader discussed earlier, fstab-sync adds the following entry:

/dev/sda1 /media/CANON_DC vfat pamconsole,noatime,sync,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0

Note the two new mount options pamconsole and managed. The former specifies that any (unprivileged) user sitting at the console may mount the file system. The latter, a no-op, specifies that this line was added by a program and not by the system administrator — hence the option managed is useful if the administrator has already manually added an entry since fstab-sync refuses to add an entry in that case.
I don't think the distro should matter too much. HAL is HAL, right ?

slothpuck 01-31-2007 01:56 PM

I'm not really sure .... thanks for that . Hmm, I'm gonna post in its entirety what I did to get to this point (in a seperate thread)v.


All times are GMT -5. The time now is 06:56 PM.