What are rc.messagebus and rc.hald for?
During Slackware 12 installation there is the question asking whether to install rc.messagebus and rc.hald. What are these two for? Can I not install them?
|
messagebus is the D-Bus daemon and hald is the HAL daemon. Neither is strictly required, but you'll find many packages use them to point that they're essentially required for a modern Linux desktop.
|
yes, you can choose not to install the packages (it's your system anyways), but i guess you will lose lots of functionality or it may not work
|
Of course it will work without these packages, but you will indeed not really lose functionality, but rather not gain it :)
|
Hello,
What does the HAL Daemon do? And what does the D-Bus daemon do? What wouldn't you be able to do if you didn't have them installed in running on your system that you could if you did? |
taken from the slack-desc
Quote:
Quote:
|
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...
|
i also use manual mounting, since i can set it up to use one single moint point
|
Hello,
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. |
All times are GMT -5. The time now is 09:05 PM. |