Date: Wed, 2 Nov 2005 13:39:31 -0800 From: Lyndon Nerenberg <lyndon@orthanc.ca> To: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem Message-ID: <154616DE-63E8-4C96-9D56-55A0FFD3CB88@orthanc.ca> In-Reply-To: <20051102162052.GB8499@odin.ac.hmc.edu> References: <43541F79.6040008@ebs.gr> <43554BCE.7090309@savvis.net> <4355FD0C.2090702@ebs.gr> <4356D12F.7000006@savvis.net> <43576A9D.1050209@ebs.gr> <4357CEA5.1000308@savvis.net> <4357D9E2.6010701@ebs.gr> <4367E346.4080106@savvis.net> <20051101224554.GA20543@odin.ac.hmc.edu> <4368018A.8040403@savvis.net> <20051102162052.GB8499@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 2, 2005, at 8:20 AM, Brooks Davis wrote:
>> ${dev}_bluetooth_config=".."
>>
>> i did not like this one because hccontrol(8) and other bluetooth
>> tools
>> do not support more than one command at a time, i.e. its not
>> possible to
>> run "hccontrol -n ubt0hci cmd1 param1 cmd2 param2". changing
>> hccontrol(8) to support this kind of syntax is somewhat tricky,
>> because
>> commands may have optional parameters.
>>
>> - have all non-default parameters appear on a separate lines, i.e.
>>
>> ${dev}_bluetooth_local_name="..."
>> ${dev}_bluetooth_hci_debug_level="..."
I would prefer these variable names take the form bluetooth_${dev}
_foo, or even better, btconf_${dev}_foo. That way all the bluetooth
config entries group together by device when rc.conf is kept sorted
by variable name. (This also follows the ifconfig_{$if} naming
convention.)
--lyndon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?154616DE-63E8-4C96-9D56-55A0FFD3CB88>