I think I've got an idea for nice feature, that may be implemented for future releases, even as huge update for its own.

As many of Us probably know, using iw package (which now don't return conflicting dependency with aircrack-ng, thanks to Mentalist Traceur) one can easily change regulatory domain:

iw reg set JP

...to Japan, which is most free of restriction domain available. US domain got upper channels (11, 12, 13) disabled, and EU got frequency limit only up to 2482000 Khz, instead of max 2494000.

Ho ever, this change isn't permanent, and even adding this line to startup script in event.d doesn't preserve from switching back to standard regulatory domain (depends on country where Your N900 originated to being sold on), cause with every Wifi off/on, domain switch back to default.

So, here is ideal place for our bellowed applet - making it optional OR strictly depending on iw, simple line of code could be added, + config option like with path to drivers - here we would just set what domain we want to set up.

Or even BETTER idea - just config option to simply (without much hassle with code, again as with defining path to bleeding edge drivers) execute ANY command after 1 second of wait, when wifi is successfully turned on (or even better, possibility to add same thing when wifi is turned out too ).

That would made great possibility for anyone to add whatever she/he want - from simple one line command as with iw example, to full-blown sophisticated script. And it wouldn't need any additional dependencies, cause it's up to user what she/he want to execute after wifi on/off (if want to execute anything). So naturally, it's suer job to put lines only depending on packages already installed.

After short personal brainstorm, i think that easiest way - writing code wise - is a configurable path to script (sh) that will be executed after 1 seconds of wait time. So, just like with path to bleeding edge driver, we set path to our external script. If none defined, applet just terminate loading/unloading process as with current version.

What do you think about it?

// Edit

Personally i could not care more if this feature will be enabled by editing config file, or with nice GUI like with path to bleeding edge location (i know that even now i can alter scripts used by applet to achieve this functionality, but that's little different thing) , but of course more user-friendly way is to do so via GUI. Having in mind that laasonen already incorporated GUI for mentioned (countless times) in this post bleeding edge driver location, it shouldn't be much work to implement such a nice and expendable feature.