Subject: Re: CVS commit: src
To: Garrett D'Amore <garrett_damore@tadpole.com>
From: Iain Hibbert <plunky@rya-online.net>
List: source-changes
Date: 09/10/2006 18:54:01
On Sun, 10 Sep 2006, Garrett D'Amore wrote:

> Jason Thorpe wrote:
> >
> > On Sep 10, 2006, at 8:45 AM, Iain Hibbert wrote:
> >
> >> etc/rc.d/btdevctl is updated to configure devices from a list
> >> in /etc/bluetooth/btdevctl.conf
> >
> > Is btevctl.conf an XML plist?  Core approved plist-format configs in
> > /etc, and it seems a shame to invent a new config format for this.
>
> To my understanding, it is _not_.  I think both plunky's and my
> understanding was that plist formats were approved for machine generated
> configs, but not human edited configs.  I think this is a human edited
> config.

No and Yes

The /etc/bluetooth/btdevctl.conf file is just a flat file listing devices
that the rc.d script will autoconfigure.  I decided this matched better
the current methodology - eg, if you twiddle a sysctl, that does not
persist across boots unless you actually edit /etc/sysctl.conf.

The XML is in /var/db/btdevctl.plist - this is a cache of the remote
device SDP query and is useful when you want to configure devices that
can't be reached (eg at boot time they may be off, or lost down the back
of the sofa)

If the .plist does not exist, then btdevctl will just attempt to query the
device and generate a new entry as it goes along. I did this by accident
the other day and impressed myself when the system rebooted.

iain