Re: [Bluez-devel] bluez-utils 2.7 default configuration

[David Woodhouse <dwmw2@infradead.org>]

On Wed, 2004-05-12 at 15:23 +0200, Marcel Holtmann wrote:
> Hi Nicholas,
> 
> > i don't get the point why there is a difference in the configuration
> > file in /etc/default/bluetooth and the init script. Or the other way
> > around: why is hidd and hid2hci activated by default?
> > I don't see any sense in this.
> 
> the bluez-utils-2.7 now contains sdpd, pand, dund and hidd. So there was
> a need for a new init script that is able to start each of these daemons
> on bootup. I enabled hidd by default, because it didn't harm if it is
> started and hid2hci makes also sense. Why should it not be started?

For the Fedora package I've put pand, dund and hidd in separate init
scripts. It's expected that individual services can be enabled or
disabled with chkconfig or system-config-services, rather than by
manually editing a separate config file. 

Also, I've often been glad of being able to restart pand _separately_
from hcid and sdpd. Doesn't sdpd forget _everything_ that's registered
when you restart it?

But hid2hci does make sense, assuming of course that you're not relying
on a Bluetooth HID device without having the Linux BT-HID support
working yet.

-- 
dwmw2