Subject: Re: /var/db/btdev.xml (from source-changes)
To: Martin Husemann <email@example.com>
From: Iain Hibbert <firstname.lastname@example.org>
Date: 07/30/2006 18:49:12
On Sun, 30 Jul 2006, Martin Husemann wrote:
> On Sat, Jul 29, 2006 at 11:57:35PM -0400, Perry E. Metzger wrote:
> > It sounds like a violation of least surprise to have the stuff in /var
> > and not /etc, then.
> I think it should be split.
There is only one part to this. We query the device and build our own
device configuration. We dont store the remote information (it might
change, its easy to get again when the device is in range)
> The configuration data, which belongs in /etc (and has no config file
> currently for itself but is only passed via command line arguments) should be
> split from the database part which could be regenerated automatically from
> interaction with the bluetooth peer using the config data from /etc.
> And the /etc part should be in some reasonably human editable format, of
Ok, is the output from prop_dictionary_externalize() considered reasonably
editable by humans?
I will move it to /etc but its going to be next weekend before I can get
to this as I've some people staying and have no time to play.