Without doubt, this is a hack. The right way to handle this would be by an overlay on /etc...
However, while the upstart job would work, the right thing to do and recommended upstream (as well as what will continue to work well in BlueZ 5) is to handle the device naming, icon, and device class/chassis information via systemd-hostnamed.
Furthermore, while that particular patch doesn't change a thing on desktop, it does make it possible to use the same logic on Touch as on Desktop to device the device name, icon, and class.
The plan with this is to use hostnamectl calls from an upstart job for now to set that information, and later hook that to the control panel to let a user change the settings.
Without doubt, this is a hack. The right way to handle this would be by an overlay on /etc...
However, while the upstart job would work, the right thing to do and recommended upstream (as well as what will continue to work well in BlueZ 5) is to handle the device naming, icon, and device class/chassis information via systemd-hostnamed.
Furthermore, while that particular patch doesn't change a thing on desktop, it does make it possible to use the same logic on Touch as on Desktop to device the device name, icon, and class.
The plan with this is to use hostnamectl calls from an upstart job for now to set that information, and later hook that to the control panel to let a user change the settings.