Re: Another pass at adapter naming

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 <hadess@xxxxxxxxxx> wrote:
> > On Thu, 2011-05-26 at 15:11 +0100, Bastien Nocera wrote:
> >> 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?


--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux