SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
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:
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 ?