Hi Dan, > > So since this may not happen for a while I figure I can give a shot. > > But I'm curious where we should get our country alpha2 from? Does LSB > > define a country has to be somewhere? Maybe the locale? Timezone? > > Anyway, in the end the user should be able to change the country too. > > > > I'm thinking to start by just letting the user pick a country for now. > > We can figure out where the hell it gets the country by default later > > but if you have ideas that'd be great. It seems reasonable to ask for > > this upon installation time (?) > > My suggestion: use the current timezone as a fallback unless the user > has specified the locale somewhere. That can obviously be done in NM or > lower, ideally we delegate this sort of thing to the supplicant and just > pass the alpha2 when NM adds the interface to the supplicant. The > addInterface() call args are just a dict, so it would be trivial to add > another item in that dict for country code. Since the country code is > global to the machine it's probably something we should just store in > the system settings service, and it's also something that probably > requires privileges to change. I would prefer if wpa_supplicant gets a global method for setting the alpha2 value. It should be dynamic and for me wpa_supplicant is the right place to handle this value. The question on how we set this value is a little bit more trickier. What we do need is a Location Manager that can use multiple source to get our current location (WiFi, GSM/UMTS, GPS etc.). Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
