Thread (25 messages) read the whole thread 25 messages, 5 authors, 2011-07-19

Re: Another pass at adapter naming

From: Bastien Nocera <hadess@hadess.net>
Date: 2011-05-26 16:12:54

On Thu, 2011-05-26 at 19:00 +0300, Luiz Augusto von Dentz wrote:
Hi Bastien,

On Thu, May 26, 2011 at 5:50 PM, Bastien Nocera [off-list ref] wrote:
quoted
On Thu, 2011-05-26 at 15:11 +0100, Bastien Nocera wrote:
quoted
As discussed on IRC,

inotify is now required, and we force hci0 (or the first device) to be
named after the pretty hostname.

Note that the GATT call isn't removed, it's now done in
adapter_update_local_name().
As discussed again, removed the default adapter special casing, and
we'll just call hci0 with the pretty name.
Does this means that the user cannot change permanently its adapter
name when pretty hostname is available? In that case I would suggest
having the stored name before pretty name otherwise if bluetoothd is
restarted the adapter name will be reset to pretty hostname again.
I don't see that as a problem. In which cases exactly would you want the
device name to be different from the pretty hostname?

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help