On 3 October 2014 10:37, Marcel Holtmann <[email protected]> wrote: > Hi Tomasz, > >>> why would we do such a thing? Integrate with systemd-hostnamed to read a >>> proper value and follow changes from systemd-hostnamed via hostnamectl >>> utility. BlueZ is happily doing it this way and so can ConnMan. >>> >> >> Ok I did not know about that. >> However, hostnamed works only with names which makes it unreliable for >> finding out the category and sub-category. >> I mean, as long as the chassis is properly filled-in that should be ok, but >> if not... I guess then it's up to the user to fix it. > > and the chassis information can be set as well. See machine-info(5) or > hostnamectl(1). > > I want this centralized in a daemon so that if users change things, they get > applied by ConnMan and BlueZ at the same time and not get out of sync.
This sounds great to me but just to double check: I will be able to set the chassis to something that makes connman use the "TV" identification for P2P, even though machine-info(5) currently does not list any appropriate chassis type? Jussi _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
