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.
hal: hal (The HAL Hardware Abstraction Layer)
hal: HAL is a piece of software that provides a view of the various
hal: hardware attached to a system. HAL keeps detailed metadata for each
hal: piece of hardware and provides hooks so that system and desktop
hal: software can react to changes in the hardware configuration (such as
hal: the insertion of a DVD, or a USB flash memory stick). Users in the
hal: "plugdev" or "cdrom" group will be able to use such devices on the
hal: desktop without the need to mount/umount them manually.
dbus: dbus (D-Bus message bus system)
dbus: D-Bus supplies both a system daemon (for events such as "new hardware
dbus: device added" or "printer queue changed") and a per user login
dbus: session daemon (for general IPC needs among user applications).
dbus: Also, the message bus is built on top of a general one-to-one message
dbus: passing framework, which can be used by any two apps to communicate
dbus: directly (without going through the message bus daemon).
Personally, I'd much rather mount my removable devices manually, so I wouldn't touch HAL with a ten foot pole. As far as D-Bus goes, I've never heard of it until just now and I'm still not sure what it does from that package description. I don't use either of them on my computer so maybe my computer doesn't count as a "modern" Linux system...
So if I got rid of HAL, exactly what functionality would cease? Auto-mounting? I mount via terminal (mount/umount command). I don't think that my printers being turned on and off count as auto-mounting either.
So if you aren't running say, Fedora, that is set up to automatically mount (and even execute a program) upon inserting a disc or plugging in a device, what is the point of having it?
I still don't know what D-Bus does? That package description isn't overtly descriptive for someone who doesn't already know what D-Bus does.
D-BUS is an inter-process communication (IPC) system. D-BUS allows programs to register, offering services to other programs. Client programs are provided the opportunity to "look up" which services are available.
Users can run several channels of D-BUS since D-BUS is implemented as a daemon. Usually there is a system channel and a private channel for each logged user. The primary mission of the system channel is to deliver signals from the HAL daemon to the processes interested in them. The mission of the private channels is to provide communication among the user's applications.
There are Glib, Qt, Python, and Java bindings for D-Bus. Lot's of applications use D-Bus like Xchat, Pidgin, libnotify, Avahi, Totem, Rhythmbox, Evince, Xorg server and others. IIRC, GNOME, KDE, and XFCE all have at least one module that require D-Bus.
I think KDE4 requires HAL, but I could be wrong. I know GNOME Volume Manager requires HAL, but most applications only have it as an optional dependency.