Re: [Bluez-devel] Device specific configuration

[Marcel Holtmann <marcel@holtmann.org>]

Hi Fredrik,

> Here's a new draft for the hcid.1 man page. It includes a description of
> hcid.conf. I propose a few modifications, detailed in the the draft, all
> possible to make backwards compatible:
> 
>    1. Device and security settings in the "options" section becomes
>       deprecated and an alias in favour of "device default". These
>       parameters are default unless specified in the "device", "device
>       <hci>" and "device <bdaddr>" sections.
> 
>    2. "enable" and "disable" becomes deprecated and aliases for
>       "yes" and "no" respectively.

please don't include stuff that I haven't yet applied. The device
specific configuration will be applied, but I haven't decided on
anything else. BTW did my patch work fine for you?

What patch brings in "device default {..."? We don't need it, because we
can use "device {..." for it.

Name the tool "Bluetooth HCI daemon", because interface is to generic.

The mailing list is still "bluez-devel@lists.sf.net" and I don't tend to
change it, because the spam stuff of SF is doing a good job.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel