can you explain to me what is it : dbus_enable="YES" and
hald_enable="YES" in file /etc/rc.conf? What is their function?
Regards,
Pawel
_______________________________________________
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"
Those enable the startup of the DBUS and HAL services via their
control files in /usr/local/etc/rc.d. Those services are often
needed for X, and programs related to X (KDE, Gnome, Xfce, and
many programs that have "Use DBUS for something" compile time
options set).
Sadly, those don't provide "man dbus" or "man hal" in a very
impolite manner. I'm sure you can find more documentation on
the web, but it may already be outdated.
If you ask what HAL and DBUS actually *ARE*, I'm not sure what
to answer - to me, they are both useless. :-)
Removing the entries in /etc/rc.conf may cause problems for some
of your programs, or may even make your X stop working properly.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
> > can you explain to me what is it : dbus_enable="YES" and
> > hald_enable="YES" in file /etc/rc.conf? What is their function?
>
> Sadly, those don't provide "man dbus" or "man hal" in a very
> impolite manner. I'm sure you can find more documentation on
> the web, but it may already be outdated.
Try "man hald".
> If you ask what HAL and DBUS actually *ARE*, I'm not sure what
> to answer - to me, they are both useless. :-)
I believe they involved with plug-and-play devices.
Robert Huff
> On Tue, 8 Jun 2010 22:54:23 +0200, Paweł Grzyb <pg.d...@gmail.com>
> wrote:
> > Hello everybody,
> >
> > can you explain to me what is it : dbus_enable="YES" and
> > hald_enable="YES" in file /etc/rc.conf? What is their function?
>
> Those enable the startup of the DBUS and HAL services via their
> control files in /usr/local/etc/rc.d. Those services are often
> needed for X, and programs related to X (KDE, Gnome, Xfce, and
> many programs that have "Use DBUS for something" compile time
> options set).
>
> Sadly, those don't provide "man dbus" or "man hal" in a very
> impolite manner. I'm sure you can find more documentation on
> the web, but it may already be outdated.
>
> If you ask what HAL and DBUS actually *ARE*, I'm not sure what
> to answer - to me, they are both useless. :-)
I believe HAL will be going away fairly soon, with its functionality
being merged into udev on Linux.
--
Bruce
Regards,
Pawel
W dniu 8 czerwca 2010 23:57 użytkownik Paul Schmehl <
pschmeh...@tx.rr.com> napisał:
> --On Tuesday, June 08, 2010 23:29:38 +0200 Polytropon <fre...@edvax.de>
> wrote:
>
>>
>> If you ask what HAL and DBUS actually *ARE*, I'm not sure what
>> to answer - to me, they are both useless. :-)
>>
>>
> hald is an interface between devices and programs. It listens for
> attachment/detachment of input devices (keyboard, mouse, etc.) and informs
> listening programs of those events.
>
> dbus is an interprocess communication system that allows programs to
> connect to and exchange messages with other programs. It allows the kernel,
> for example, to interact with your desktop. Rather than you interacting
> directly with the kernel, dbus acts as a middle man, controlling the
> communications between the two and only allowing you to perform actions
> which are considered "safe" or "reasonable".
>
> The two work together, for example, to let your desktop know when you
> connect a new mouse or type on your keyboard.
>
> --
> Paul Schmehl, Senior Infosec Analyst
> As if it wasn't already obvious, my opinions
> are my own and not those of my employer.
> *******************************************
> "It is as useless to argue with those who have
> renounced the use of reason as to administer
> medication to the dead." Thomas Jefferson
hald is an interface between devices and programs. It listens for
attachment/detachment of input devices (keyboard, mouse, etc.) and informs
listening programs of those events.
dbus is an interprocess communication system that allows programs to connect to
and exchange messages with other programs. It allows the kernel, for example,
to interact with your desktop. Rather than you interacting directly with the
kernel, dbus acts as a middle man, controlling the communications between the
two and only allowing you to perform actions which are considered "safe" or
"reasonable".
The two work together, for example, to let your desktop know when you connect a
new mouse or type on your keyboard.
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
_______________________________________________