[arch-projects] [netcfg] Reviewing old code: custom control paths

Jouke Witteveen j.witteveen at gmail.com
Tue Jul 3 07:59:02 EDT 2012

Dear Rémy,

I came across commit a1fc1 to netcfg. It refers FS#24949 both in the
commit message and the comments. That bug looks completely unrelated.
Can you elaborate why it was/is needed to support custom control
paths? Dealing with WPA_CTRL_PATH makes for messy code, currently. I
guess if we want to go with supporting it, someone should write a
wpa_cli wrapper that
1) uses WPA_CTRL_PATH if it is set, or extract it (currently
connections/ethernet and connections/wireless duplicate code)
2) else determines WPA_CTRL_PATH from th profile that is active on the interface
3) else uses a default value

I'd rather go back to the situation with a fixed control path (but
please, convince me of the need of custom paths). Additionally,
extraction from the profile is not always right as it could interpret
ctrl_interface values that are not directories as directories.

- Jouke

More information about the arch-projects mailing list